Google Search API for real-time web results
Search Google over HTTP and receive titles, links, and snippets as structured JSON, with the option to return page content in the same request.
Endpoint
Results arrive in the same JSON shape as every other engine, so one parser covers all of them.
Clean titles, without the scraping artefacts.
The result description, sometimes prefixed with a date.
Set crawl_results and the top results return markdown.
Useful for
AI answers / RAG / Research
The default engine, and the fallback for the rest
Google is the default `search_service`, so a request without the parameter searches it. The endpoint, the authentication, and the response shape are shared with every other engine, which is what makes switching sources a one-field change.
Search and page content in one call
`crawl_results` fetches the top N results and returns each as markdown, so an answer does not need a second round trip to read its sources.
Domain and time filters
`include_sites` and `exclude_sites` narrow to or away from specific domains, and `time_range` restricts to a day, week, month, or year.
Batch queries in one request
The endpoint accepts an array of query objects, billed item by item, with failed items not charged.
One contract, 17 engines
Moving a query from Google to Reddit, GitHub, or the Chinese engines is a change of one field, not a new integration.
What is a Google search API?
A Google search API is an HTTP interface that returns Google web results as structured data. Google does not sell general web search as a simple developer API β its Custom Search JSON API is scoped and quota-limited, and Gemini grounding returns an answer rather than a result list β so applications that need a ranked list of live web results use a search API in front of it. Search1API returns titles, links, and snippets as JSON, optionally with the page content of the top results in the same response, and uses the same request and response shape for its other 16 engines. For an agent, that consistency is the point: the same code path covers general web search, community sources, and the Chinese-language web.
Typical workflow
Search Google over HTTP and receive titles, links, and snippets as structured JSON, with the option to return page content in the same request.
Send a query, optionally with `search_service` set to `google`.
Read the structured result list of titles, links, and snippets.
Set `crawl_results` when the answer needs page content rather than links.
One request, results and their content
A single call searches Google and, with `crawl_results`, returns the body of the top results as markdown, so a grounded answer takes one round trip instead of three.
bash
Best for
AI assistants that need current web evidence before answering.
RAG pipelines that retrieve and read sources in one step.
Research and monitoring tools that need a ranked list rather than a summary.
Applications that combine general web search with vertical sources.
FAQ
Is there an official Google search API?
Google offers the Custom Search JSON API, which is scoped to configured search engines and carries a low free quota, and Gemini grounding, which returns a synthesised answer rather than a ranked result list. Neither is a general-purpose web search API, which is why applications use a search API in front of Google.
Do I need a Google API key?
No. Authentication is your Search1API key. The request is a POST to https://api.search1api.com/search, and `google` is the default `search_service`.
Can I get page content with the results?
Yes. Set `crawl_results` to the number of top results you want fetched, and each page retrieved successfully includes a `content` field with the page text as markdown. Pages that cannot be retrieved are returned without `content` and are not charged.
What does a Google search cost?
One credit per search, and one additional credit for each page retrieved successfully through `crawl_results`. At the base top-up rate of $1 for 1,000 credits, that is $1 per 1,000 searches. Signup includes 100 free credits with no credit card, and top-up credits do not expire.
Can I filter by domain or date?
Yes. `include_sites` and `exclude_sites` take domain lists, and `time_range` accepts day, week, month, or year.
Which other engines are supported?
The same Search endpoint accepts `duckduckgo`, plus vertical sources such as `reddit`, `x`, `github`, `arxiv`, `youtube`, `wikipedia`, and `imdb`, and the Chinese-language engines `baidu`, `360`, `quark`, `wechat`, and `bilibili` β 17 in total on one contract.