# Google — API Agent Score

> Score: 58/100 (Grade: D) | Domain: google.com | Rubric: 1.0.0 | Checked: July 24, 2026

Google scored 58/100 (D), classified "not-ai-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/google)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 58/100 (D)
- Classification: not-ai-ready

## Category Scores

- API Design: 86/100 (A)
- Developer Experience: 55/100 (D)
- Agent Discovery: 66/100 (C)
- Agent Understanding: 58/100 (D)
- Agent Usability: 41/100 (F)

## Check Results

### API Design

- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: spec 100%, docs 100%, wellknown 0%.
- [warn] Machine-readable, versioned contract — info.version="1.0.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%.
- [warn] Schema coverage & depth — Only 37% of operations have documented schemas. Investigated: spec 61%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 100%.
- [pass] Example coverage — 0% example coverage. Investigated: spec 100%, docs 0%.

### Developer Experience

- [pass] Description completeness — 84% description completeness (target 90%+). Investigated: spec 100%.
- [pass] Changelog published — changelog documented in the docs site at https://docs.cloud.google.com/release-notes. Investigated: spec 100%, docs 100%, sdk 100%.
- [warn] Quickstart present — Quickstart page reachable (2 variants scanned starting at https://docs.cloud.google.com/docs/get-started?hl=ko) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [fail] Self-service developer portal — No signup page detected across conventional paths (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free). Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 15 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (langchain-ai/langchain-google, 291 snippets). Investigated: docs 100%, sdk 100%, cli 100%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.
- [fail] llms.txt present, valid & comprehensive — No /llms-full.txt found at the candidate origins. Investigated: docs 0%.
- [skip] Docs reachable, not hard auth-gated — No surface produced evidence for this capability in this run.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Only 2 distinct 4xx/5xx codes documented (plus 0 "default" catch-all responses). Investigated: docs 100%, spec 50%.
- [warn] Operation purpose clarity — 0% of operations are agent-inferable. Investigated: spec 17%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 1 assessed pages (1 JS-rendered). Investigated: docs 0%.
- [skip] Agent-navigable, token-efficient docs — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [warn] Runnable collection with test scripts — No test scripts found in the workspace's collections. Investigated: platform 50%.
- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [fail] Pagination documented & consistent — 4 list endpoint(s) exist but no pagination params found. Investigated: spec 0%, docs 0%.
- [fail] Sandbox separation — No sandbox/test server declared across 12 server entries; no test-key prefixes documented. Investigated: spec 0%, docs 0%.

## Executive Summary

Google's API design and contract quality are strong, giving partners a solid technical foundation to build on. However, the program has critical gaps in operational reliability, safe integration, and agent discoverability that will block partners and their AI agents from reaching production confidently. The highest priority is making APIs trustworthy and executable at scale — covering idempotency, rate-limit signaling, pagination, and sandbox access — followed closely by opening the agent discovery front door with llms.txt, structured docs, and an AGENTS.md context file. Closing these gaps will let partners and their agents self-serve from first call to full integration without a support escalation.