# Gmail — API Agent Score

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

Gmail scored 54/100 (D), classified "not-ai-ready".

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

## Summary

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

## Category Scores

- API Design: 70/100 (B)
- Developer Experience: 52/100 (D)
- Agent Discovery: 66/100 (C)
- Agent Understanding: 40/100 (F)
- Agent Usability: 53/100 (D)

## Check Results

### API Design

- [warn] Schema coverage & depth — 6/7 (86%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 87%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%.
- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 0%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Auth declared & discoverable — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Description completeness — 6/6 operations carry a description. Investigated: sdk 100%.
- [pass] Changelog published — Newest official SDK activity 0 day(s) ago. Investigated: sdk 100%.
- [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] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [skip] Code samples in docs — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Discovered SDKs in 7 distinct languages. Investigated: sdk 100%, docs 0%, cli 0%.
- [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%, sdk 0%.
- [skip] Docs reachable, not hard auth-gated — No surface produced evidence for this capability in this run.

### Agent Understanding

- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [skip] Machine-readable errors (RFC 9457) — No surface produced evidence for this capability in this run.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.
- [skip] Agent-navigable, token-efficient docs — No surface produced evidence for this capability in this run.
- [skip] Docs structured data — 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

- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%.
- [fail] Idempotency documented — No built-in retry machinery was found; transient failures are not retried. Investigated: sdk 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Gmail's API program shows strength in schema design but has significant gaps in two areas that directly affect partner success: developer onboarding and agent readiness. Partners currently lack a self-service portal and quickstart path, meaning they cannot get hands-on without friction or a sales conversation. Simultaneously, agents have no structured instructions, no machine-readable discovery file, and no runnable examples to build against — making autonomous integration unreliable. Prioritize closing the onboarding and agent-context gaps first, then lock down idempotency documentation and security hygiene to make the program trustworthy at scale.