canonical: https://jentic.com/apis/goog.io/goog

# goog.io | Unofficial Google Search API

Jentic publishes the only available OpenAPI specification for goog.io | Unofficial Google Search API, keeping it validated and agent-ready. The goog.io API exposes 6 endpoints for running Google web search, image search, news search, page crawling, and SERP retrieval programmatically without managing proxies. Endpoints accept a query as a path parameter and return clean structured results, with optional language, country, and locality parameters for geographic targeting. Authentication is an apikey header.

## For AI agents

Run Google web, image, news, crawl, and SERP queries via 6 endpoints with country and language targeting on goog.io.

## Scope

Does not handle JavaScript page rendering, indexing your own site in Google, or paid ad placement - use for unofficial Google web, image, news, crawl, and SERP retrieval only.

## Capabilities

- Run a Google web search and return ranked organic results
- Search Google Images with country and language localisation
- Fetch Google News results for a query and time window
- Crawl a target query through goog.io's USA-IP infrastructure
- Retrieve a full Google SERP for ranking and SEO research
- Check service status before issuing search jobs

## Use cases

### SEO Rank Tracking

SEO teams pull Google SERPs for tracked keywords daily and write the results into a dashboard. POST `/v1/serp`/ returns the structured SERP, and the country and language parameters let teams track rank changes per market in one job.

Example prompt: Call POST `/v1/serp`/ for the keyword 'best crm API' in the US and UK markets and store the top 10 organic positions.

### News Monitoring

Brand and competitive teams call `/v1/news/{query}` every hour for tracked terms, dedupe results, and feed them into a Slack channel. The infrastructure handles the proxy and IP rotation problem that makes do-it-yourself Google scraping fragile.

Example prompt: Pull `/v1/news/competitor-name` every 30 minutes and post any article from the last hour into the #news channel.

### Lead Research Crawling

Sales and BD teams crawl Google for prospect-related queries and feed the result into an enrichment pipeline. `/v1/crawl/{query}` returns clean USA-IP results, which avoids the captchas and IP bans that DIY scrapers hit at scale.

Example prompt: For each prospect company in the CRM, crawl '{company} pricing' and store the top 5 result URLs.

### AI Research Agent via Jentic

An AI research agent uses goog.io as its 'fresh web' tool through Jentic. The agent searches Jentic for a Google search operation, loads the schema, and executes - Jentic injects the apikey header so the agent only handles the query, country, and language.

Example prompt: Search Google for the user's question, take the top 5 organic URLs, and pass them to a downstream summarisation step.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/` | Service status |
| GET | `/v1/search/{query}` | Google web search |
| GET | `/v1/images/{query}` | Google Images search |
| GET | `/v1/news/{query}` | Google News search |
| GET | `/v1/crawl/{query}` | Google crawl |
| POST | `/v1/serp/` | Full Google SERP |

## Key resources

- **Search** — Google web search by query path parameter
- **Images** — Google Image search results
- **News** — Google News search results
- **SERP** — Full Google SERP for a query
- **Crawl** — USA-IP crawl of a Google query
- **Status** — Service status check

## Why Jentic

- **Setup:** Wiring goog.io by hand means passing the apikey header against api.goog.io, scoping to one subscription, and mapping the web, image, news, crawl, and SERP retrieval endpoints yourself. Through Jentic you install once, import goog.io from the API Directory, store the apikey once, and your agent calls it.
- **Permission scoping:** goog.io carries the query in the URL path segment rather than a persistent resource id, so scope the agent to the operations it needs, such as web search or image search. You choose the operations it may call, so ones like the crawl endpoint or the SERP POST are not included unless you add them.
- **Credential handling:** Your goog.io apikey is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'google web search' or 'search for news', and Jentic returns the matching goog.io operation with its parameter schema so the agent calls the right endpoint without reading the reference.

## Related APIs

- **Google Custom Search JSON API** — Google's official Custom Search API, scoped to a Programmable Search Engine you configure.
- **Google Custom Search JSON API** — Pair the official API with goog.io when you also need raw web SERPs and news.
- **Giphy** — Pair when the agent's research output also needs visual GIF media for chat replies.

## FAQ

### Why is there no official OpenAPI spec for goog.io | Unofficial Google Search API?

goog.io does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call goog.io | Unofficial Google Search API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the goog.io API use?

goog.io uses an apiKey scheme on the apikey header. Through Jentic the key is stored encrypted in the vault and scoped to your goog.io subscription, so the raw key never enters the agent's context.

### Can I run a Google SERP query with goog.io?

Yes. POST `/v1/serp`/ accepts a query and optional country, language, and locality parameters and returns the structured SERP, including organic positions and any rich result blocks Google rendered.

### What are the rate limits for the goog.io API?

goog.io enforces per-subscription rate limits visible in your account dashboard. The OpenAPI spec does not encode exact numbers, so check the dashboard before running large rank-tracking jobs - pace concurrent requests rather than firing them in tight loops.

### How do I run a Google search through Jentic?

Search Jentic for 'google web search', load the schema for GET `/v1/search/{query}`, and execute with the encoded query in the path. Jentic injects the apikey header so the agent only supplies the query and any localisation parameters.

### Does the API return JavaScript-rendered content?

No. The endpoints return Google's results pages and crawled URLs as text or JSON; they do not execute JavaScript on the destination pages. For full-page rendering, fetch each result URL with a headless browser API.

### Can I limit what my agent is allowed to do with the goog.io API?

Yes. Because you run Jentic One yourself, your own rules decide which goog.io operations the agent may call, so you can allow just web search on GET `/v1/search/{query}` or image search on GET `/v1/images/{query}` and leave the rest out. Since goog.io carries the query in the URL path rather than a persistent resource id, you scope by operation, meaning higher-reach calls like the `/v1/crawl/{query}` endpoint or the POST `/v1/serp`/ SERP retrieval are not available to the agent unless you add them. Your goog.io apikey is held by your own instance and injected only for the operations you permit, so it never reaches the agent's context.