# Sanity — API Agent Score

> Score: 78/100 (Grade: B) | Domain: sanity.io | Rubric: 1.0.0 | Checked: July 29, 2026

Sanity scored 78/100 (B), classified "partially-ready".

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

## Summary

- Overall: 78/100 (B)
- Classification: partially-ready

## Category Scores

- API Design: 64/100 (C)
- Developer Experience: 68/100 (C)
- Agent Discovery: 97/100 (A+)
- Agent Understanding: 73/100 (B)
- Agent Usability: 86/100 (A)

## Check Results

### API Design

- [warn] Machine-readable, versioned contract — `--help --format json` exits 0 but output is not JSON. Investigated: cli 75%.
- [warn] Schema coverage & depth — 10 of 79 public signatures use loose types (anyTypeRatio=0.127). Investigated: sdk 70%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, cli 100%, docs 0%.
- [warn] Security & governance hygiene — security.txt present but missing or expired Expires. Investigated: wellknown 50%.
- [fail] Auth declared & discoverable — no auth/config hint in --help. Investigated: cli 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://www.sanity.io/get-started; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Changelog published — Newest official SDK activity 0 day(s) ago. Investigated: sdk 100%.
- [warn] Quickstart present — Quickstart page reachable (3 variants scanned starting at https://www.sanity.io/docs/getting-started) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [warn] Description completeness — 31/50 operations lack a description. Investigated: sdk 38%.
- [fail] Code samples in docs — No detectable code samples across 20 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] llms.txt present, valid & comprehensive — llms.txt found at 2 locations; using https://www.sanity.io/docs/llms.txt as canonical. Investigated: docs 100%, sdk 0%.
- [pass] Docs reachable, not hard auth-gated — All 50 sampled pages are publicly accessible. Investigated: docs 100%.
- [pass] Registry & SDK presence — Indexed on Context7 (websites/sanity_io, 16126 snippets). Investigated: docs 100%, cli 100%, sdk 67%, mcp 0%, wellknown 0%.
- [warn] Crawlable / AEO — Sitemap present (6 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Single base error "BaseException" with 6 subclasses. Investigated: sdk 100%, cli 0%.
- [warn] Agent-navigable, token-efficient docs — 2 of 2 page(s) with tab headers don't distinguish between variants. Investigated: docs 80%.
- [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 3 assessed pages (3 JS-rendered). Investigated: docs 0%.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 0 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%, cli 0%.
- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%.
- [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

Sanity's API program shows strong crawlability and discoverability, but partners and their AI agents are held back by two compounding gaps: missing machine-readable agent context and structured documentation signals make it hard for agents to reliably understand and act on the API surface, while the absence of runnable, test-backed collections means partners can't validate real workflows without significant manual effort. Prioritize closing the agent-understanding gaps first — they block every downstream integration — then add executable, verifiable onboarding artifacts to accelerate partner time to production.