Google Developer Knowledge API: Stop Your AI Agent Hallucinating Docs

The short answer

Google's Developer Knowledge API gives AI agents programmatic access to Google's official developer documentation as clean, frequently-indexed Markdown. Four methods cover the whole retrieval loop: search chunks, fetch one or many full documents, and get a grounded answer with references. You can call it from the gcloud CLI, as an MCP tool, or through official client libraries. If your agent touches Google Cloud, Firebase, or Android, this is now the official source of truth.

What the API actually is

On October 7, 2026, Google technical writer Christina Gonzalez published a Developers Blog post laying out the full picture: the Developer Knowledge API is Google's official machine-readable documentation layer, built specifically for AI agents, IDE extensions, automated workflows, and production applications. It had been in public preview earlier in 2026; by early October it reached its general-availability milestones, with the gcloud CLI commands going GA on September 22, 2026.

The corpus is the part that matters. At last count it spans Google's public developer properties: Google Cloud docs, Firebase, Android, Chrome, Apigee, Fuchsia, TensorFlow, web.dev, ai.google.dev, and the main developers.google.com surface. Content arrives as structured Markdown, not scraped HTML, and Google says the index refreshes frequently, which shrinks the lag between a documentation update and your agent seeing it. That is the whole value proposition in one line: when a flag gets deprecated on a Tuesday, your agent stops recommending it on Wednesday.

The four methods and the two-step pattern

The REST surface is deliberately small. Each method does one job, and they chain into a retrieval pattern that is cheap on tokens:

The pattern Google intends is two-step. First, search chunks to find candidate pages. Then fetch the full Markdown only for the winners, using the exact parent resource the search returned rather than constructing document names from memory. A search result is chunks, not guaranteed full pages, so a robust client groups duplicate chunks by parent before fetching; otherwise one page can eat several retrieval slots while adding almost no new context.

Why does this matter for your bill? Because the expensive part of RAG is not the retrieval call, it is the context you stuff into the model. Searching first and fetching second means the model only ever sees the pages that earned their place. That is the same discipline behind good routing in any agent stack: retrieve narrow, expand only on evidence.

Three ways to plug it into your agent

Pick the path that matches where your agent already lives.

1. gcloud CLI: the fastest way to try it

   Enable the API in your Google Cloud project, then query straight from the terminal. The developer-knowledge command group went GA on September 22, 2026, and Cloud Shell ships with it preinstalled:

   bash

   Copy

   gcloud developer-knowledge answer-query \
     --query="How do I create a Cloud Storage bucket with uniform access?"
   gcloud developer-knowledge documents search-chunks \
     --query="Cloud Run minimum instances pricing"
   gcloud developer-knowledge documents describe \
     --document="documents/docs.cloud.google.com/storage/docs/creating-buckets"

   This is the path for scripts, cron jobs, and quick checks. No SDK, no server, just answers grounded in the official docs.

2. MCP server: give your agent a docs tool

   Point any MCP-compatible agent at Google's hosted server with an API key header, and documentation search becomes a tool call your agent can make on its own:

   bash

   Copy

   mcp add developer-knowledge \
     --type http \
     --url "https://developerknowledge.googleapis.com/mcp" \
     --header "X-Goog-Api-Key" "${DEVELOPERKNOWLEDGE_API_KEY}"

   This is the configuration pattern from public agent setups using Gemini CLI and similar tools. Once registered, the agent decides when it needs fresh docs instead of you hardcoding retrieval into every prompt. Google also ships a dedicated developer plugin for AI coding agents that bundles this: for Claude Code, Codex CLI, and Antigravity CLI, you enable the API in your project, create an API key, and export DEVELOPERKNOWLEDGE_API_KEY before starting the agent.

3. Client libraries: build the retrieval layer yourself

   Official libraries exist for Python, Node.js and TypeScript, Go, Java, PHP, and Ruby, plus raw REST and gRPC endpoints. This is the path when you want control: custom chunking strategies, a local cache of fetched documents, merged results from your own private docs alongside Google's, or a review step before the agent acts on what it retrieved. If you already run a backend service, start here and build a governed retrieval layer instead of letting every agent call the API directly.

Developer Knowledge API vs the alternatives

You have four realistic options for keeping an agent current on docs. Here is how they compare on the dimensions that actually decide the choice:

Two notes on that last row. Context7 is the incumbent here for a reason: public adoption tracking puts it at roughly 3.45 million npm downloads a month and 62,000 GitHub stars, which is distribution that is hard to argue with for general library docs. But community extracts are still somebody's scrape of somebody's docs. When the question is specifically about Google's platforms, the official API wins on authority: there is no middleman whose crawler might be a week behind.

The honest architecture for most production agents is a hybrid. Use the Developer Knowledge API as the authoritative layer for Google's docs, your own vector store for private and third-party material, and web search only for what neither covers. Each layer answers the questions it is actually qualified to answer.

What it costs

Google has not published per-request pricing for this API. What is documented: it is free to enable and use under standard developer limits, with request allocations managed through the Google Cloud Quotas and System Limits page for your project. One practitioner tutorial building a support assistant on it describes the API as fully managed by Google at zero additional infrastructure cost on their side.

The cost story that matters more is tokens. The two-step pattern exists to keep your LLM bill down: chunk search is cheap, and full documents only enter context for the pages that matter. Compare that with the naive alternative of pasting entire documentation pages into prompts, or worse, letting the agent retry three times on hallucinated flags. The cheapest token is the one you never send, and the second cheapest is one spent on verified Markdown instead of a guess.

When it is the wrong tool

No tool survives contact with the wrong job. Do not reach for this API when your agent needs your company's private runbooks, a third-party SDK, or the general web; the corpus is Google's public developer documentation and nothing else. AnswerQuery is bounded to that corpus by design, so questions outside it get no answer rather than a creative one, which is a feature, not a bug. And if you need deterministic, audited retrieval with your own chunking and access controls, build the client-library layer rather than handing the agent a raw tool and hoping.

Where to build and compare

Every tool below is a real link to the official source. If you ground agents for a living, these are the bookmarks that pay.

Stop shipping stale answers

The pattern behind this post is a consulting product wearing a blog post's clothes. Teams building agents in 2026 do not have a model problem; they have a grounding problem. Their agents answer from training data, nobody owns the retrieval layer, and the first time anyone notices is when a customer pastes a hallucinated command into production. I help teams and founders design exactly that layer: which corpus answers which question, the search-then-fetch discipline that keeps token bills sane, and the acceptance checks that catch a stale answer before it ships. If your agent touches Google Cloud and still scrapes docs, that is a week of work, not a rewrite. Details are on my about page.

“

Your agent is only as current as its retrieval layer. Point it at the official docs, search before you fetch, and stop letting training data answer questions the documentation already settled.

”

FAQ

What is Google's Developer Knowledge API?

It is a Google Cloud API that gives AI agents programmatic access to Google's official developer documentation as clean, frequently-indexed Markdown. Instead of scraping docs sites or relying on stale training data, your agent searches chunks, pulls full pages, and gets grounded answers straight from the official source.

When did the Developer Knowledge API launch?

It entered public preview earlier in 2026 with an MCP server, and hit general-availability milestones in early October 2026. The gcloud CLI commands went GA on September 22, 2026, and a Google Developers Blog post by technical writer Christina Gonzalez laid out the full picture on October 7, 2026.

What are the four methods and how do they work together?

SearchDocumentChunks finds relevant page URIs and content snippets for a query. GetDocument and BatchGetDocuments pull the complete Markdown for one or many results. AnswerQuery generates a response drawn strictly from the documentation corpus. The intended pattern is two-step: search first, then fetch full pages, which keeps token usage low.

How do I connect it to Claude Code or my own agent?

Three paths. One, the gcloud CLI: enable the API in your Google Cloud project and use the developer-knowledge command group. Two, the MCP server at developerknowledge.googleapis.com/mcp with an API key header, which tools like Claude Code, Gemini CLI, and crush can call as a tool. Three, official client libraries for Python, Node.js/TypeScript, Go, Java, PHP, and Ruby, plus Google's developer plugin for Claude Code, Codex CLI, and Antigravity CLI.

How much does the Developer Knowledge API cost?

Google has not published per-request pricing. A Google Cloud tutorial describes it as free to enable and use under standard developer limits, with quotas managed through the Google Cloud Quotas page. The two-step search-then-fetch pattern also keeps your LLM token spend down, since the agent only pulls full pages for the chunks that matter.

When should I not use the Developer Knowledge API?

When your agent needs anything outside Google's public developer docs. The corpus covers Google Cloud, Firebase, Android, Chrome, TensorFlow, web.dev, and sibling properties, but not your private docs, third-party SDKs, or the general web. For those, pair it with your own vector store or a general web-grounding tool.