# Airtable — API Agent Score

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

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

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

## Summary

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

## Category Scores

- API Design: 87/100 (A)
- Developer Experience: 60/100 (C)
- Agent Discovery: 93/100 (A+)
- Agent Understanding: 49/100 (F)
- Agent Usability: 78/100 (B)

## Check Results

### API Design

- [pass] Schema coverage & depth — 18/18 (100%) public params are fully typed (no any/**kwargs). Analyzer confirms all methods have a derivable input schema. Investigated: sdk 100%.
- [pass] Example coverage — Code samples present on 6/19 pages across 1 language(s); broader multi-language coverage missing. Investigated: docs 100%, sdk 100%.
- [warn] Security & governance hygiene — security.txt present but missing or expired Expires. Investigated: wellknown 50%.
- [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] Self-service developer portal — Signup page at https://airtable.com/signup; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Code samples in docs — Code samples present on 6/19 pages across 1 language(s); broader multi-language coverage missing. Investigated: docs 100%.
- [warn] Description completeness — 38/39 operations lack a description. Investigated: sdk 3%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Changelog published — Official SDKs stale: newest activity 412 days ago. Investigated: sdk 0%.

### Agent Discovery

- [pass] Docs reachable, not hard auth-gated — All 50 sampled pages are publicly accessible. Investigated: docs 100%.
- [pass] Registry & SDK presence — Indexed on Context7 (airtable/blocks, 595 snippets). Investigated: docs 100%, sdk 100%, mcp 100%, cli 0%, wellknown 0%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 50 sampled pages. Investigated: docs 75%, sdk 0%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — 50 of 50 sampled pages have content starting past 50% (worst 100%). Investigated: docs 90%.
- [fail] Machine-readable errors (RFC 9457) — No single common SDK base error class was found; errors do not share one root. Investigated: sdk 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 1 assessed pages (1 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 1 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%.
- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%.
- [warn] Runnable collection with test scripts — No test scripts found in the workspace's collections. Investigated: platform 50%.
- [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

Airtable's API program shows real strength in API design, auth security, and agent discoverability — partners can find the APIs without friction. The critical gaps are in agent understanding and developer onboarding: there are no machine-readable error bodies, no agent instruction file, no structured docs data, and no quickstart — meaning partners and their AI agents must guess at error handling and onboard through trial and error rather than a guided path. Closing the agent-understanding gaps and adding a clear onboarding quickstart should be the immediate priorities to unlock self-serve partner growth.