# Supabase — API Agent Score

> Score: 72/100 (Grade: B) | Domain: supabase.com | Rubric: 1.0.0 | Checked: July 24, 2026

Supabase scored 72/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 88/100 (A)
- Developer Experience: 94/100 (A+)
- Agent Discovery: 79/100 (B)
- Agent Understanding: 42/100 (F)
- Agent Usability: 78/100 (B)

## Check Results

### API Design

- [pass] Schema coverage & depth — 13/13 (100%) public params are fully typed (no any/**kwargs). Analyzer confirms all methods have a derivable input schema. Investigated: sdk 100%, spec 50%.
- [pass] Auth declared & discoverable — authentication documented in the docs site at https://supabase.com/auth. Investigated: spec 100%, docs 100%.
- [warn] Machine-readable, versioned contract — info.version="0.0.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%.
- [pass] Example coverage — Code samples in 5 language(s) across docs (top: shell, javascript, typescript); 2/19 pages have ≥ 2 languages on the same page. Investigated: docs 100%, sdk 100%, spec 0%.
- [warn] Security & governance hygiene — security.txt present but missing or expired Expires. Investigated: wellknown 50%, spec 0%.

### Developer Experience

- [pass] Self-service developer portal — Self-service signup at https://supabase.com/dashboard/sign-up; free tier / sandbox documented. Investigated: docs 100%.
- [pass] Quickstart present — Quickstart at https://supabase.com/docs/guides/getting-started/architecture with a runnable first-call sample. Investigated: docs 100%.
- [pass] Code samples in docs — Code samples in 5 language(s) across docs (top: shell, javascript, typescript); 2/19 pages have ≥ 2 languages on the same page. Investigated: docs 100%.
- [pass] Changelog published — changelog documented in the docs site at https://supabase.com/changelog. Investigated: spec 100%, docs 100%, sdk 100%.
- [warn] Description completeness — 161/379 operations lack a description. Investigated: sdk 58%, spec 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (supabase/supabase, 21416 snippets). Investigated: docs 100%, sdk 100%, cli 100%, mcp 100%, wellknown 0%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 48 sampled pages; 2 failed to fetch. Investigated: docs 69%, sdk 0%.
- [warn] Docs reachable, not hard auth-gated — 5 of 49 sampled pages return 200 for non-existent URLs (soft 404); 1 failed to fetch. Investigated: docs 60%.
- [warn] Crawlable / AEO — Sitemap present (2 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — 10 of 37 pages have substantive content differences between markdown and HTML (avg 14% missing). Investigated: docs 40%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (docs, sdk) is 7% (threshold 35% for full credit).
- [fail] Machine-readable errors (RFC 9457) — No 4xx/5xx response codes (or default error response) documented anywhere in the spec. Investigated: spec 0%, docs 0%, sdk 0%.
- [fail] Operation purpose clarity — 0% of operations are agent-inferable. Investigated: spec 0%.
- [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 6 assessed pages (2 JS-rendered). Investigated: docs 0%.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%, spec 0%, docs 0%.
- [pass] Pagination documented & consistent — Pagination params detected on 1 list endpoint(s). Investigated: spec 100%, docs 100%, sdk 0%.
- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%, spec 0%, docs 0%.
- [warn] Runnable collection with test scripts — No test scripts found in the workspace's collections. Investigated: platform 50%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.

## Executive Summary

Supabase's API program is in strong shape for developer experience and API design, where partners can already build with confidence against a well-structured contract. However, the program has a critical blind spot in agent understanding: errors are not machine-readable, operations lack purpose clarity, there is no agent instructions file, and docs carry no structured data — meaning AI agents attempting to integrate autonomously will guess, fail silently, or hallucinate behavior. Fixing the agent understanding layer is the highest-leverage move, followed by closing the rate-limit signaling gap that undermines reliability for automated partner workflows.