# Vercel — API Agent Score

> Score: 89/100 (Grade: A) | Domain: vercel.com | Rubric: 1.0.0 | Checked: July 22, 2026

Vercel scored 89/100 (A), classified "ai-ready".

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

## Summary

- Overall: 89/100 (A)
- Classification: ai-ready

## Category Scores

- API Design: 94/100 (A+)
- Developer Experience: 100/100 (A+)
- Agent Discovery: 82/100 (A)
- Agent Understanding: 79/100 (B)
- Agent Usability: 92/100 (A+)

## Check Results

### API Design

- [pass] Auth declared & discoverable — authentication documented in the docs site at https://vercel.com/login?next=%2Fauthentication. Investigated: docs 100%, wellknown 100%, spec 50%, cli 0%.
- [warn] Schema coverage & depth — 663/664 (100%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 100%, spec 67%.
- [warn] Machine-readable, versioned contract — info.version="0.0.1" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%, cli 50%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 100%.
- [pass] Example coverage — Code samples in 4 language(s) across docs (top: typescript, curl, python); 7/20 pages have ≥ 2 languages on the same page. Investigated: docs 100%, sdk 100%, spec 0%, cli 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://vercel.com/signup (CSR-rendered — body classifier inconclusive); free tier / sandbox documented in pricing/docs. Investigated: docs 100%.
- [pass] Quickstart present — Quickstart at https://vercel.com/docs/getting-started-with-vercel has a runnable sample in the .md variant (https://vercel.com/docs/getting-started-with-vercel.md). Investigated: docs 100%.
- [pass] Code samples in docs — Code samples in 4 language(s) across docs (top: typescript, curl, python); 7/20 pages have ≥ 2 languages on the same page. Investigated: docs 100%.
- [pass] Description completeness — 82% description completeness (target 90%+). Investigated: spec 100%, sdk 96%.
- [pass] Changelog published — changelog documented in the docs site at https://vercel.com/changelog. Investigated: spec 100%, docs 100%, sdk 100%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/vercel, 16576 snippets). Investigated: docs 100%, cli 100%, mcp 100%, sdk 83%, wellknown 0%.
- [warn] Docs reachable, not hard auth-gated — 1 of 50 sampled pages return 200 for non-existent URLs (soft 404). Investigated: docs 75%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 49 sampled pages; 1 failed to fetch. Investigated: docs 56%, sdk 0%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 18 distinct 4xx/5xx response codes documented. Investigated: docs 100%, sdk 100%, spec 50%, cli 0%.
- [pass] Operation purpose clarity — 96% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — 19 of 49 pages have substantive content differences between markdown and HTML (avg 30% missing); 1 failed to fetch. Investigated: docs 61%.
- [pass] Docs structured data — JSON-LD Article markup on 12/20 assessed pages (60%) with dateModified present. Investigated: docs 100%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 3 surfaces (spec, docs, sdk) is 3% (threshold 35% for full credit).
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%, spec 0%, docs 0%, cli 0%.
- [pass] Rate-limit signaling — rate-limit behavior documented in the docs site at https://vercel.com/docs/limits. Investigated: spec 100%, docs 100%.
- [pass] Pagination documented & consistent — Pagination params detected on 17 list endpoint(s). Investigated: spec 100%, docs 100%, sdk 20%.
- [pass] Sandbox separation — sandbox documented in the docs site at https://vercel.com/docs/sandbox. Investigated: spec 100%, docs 100%, sdk 100%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.

## Executive Summary

Vercel's API program shows strong foundations in API design and discoverability, but two gaps are holding back partner and agent success. The most urgent is the absence of an agent instructions file, which means AI coding agents lack the structured context they need to work with your APIs without hallucinating or guessing. Close behind is the lack of a runnable collection with test scripts, which forces partners to build against static docs rather than verified, executable truth. Closing these two gaps will meaningfully accelerate how quickly partners — and the AI agents they rely on — can move from discovery to working integrations.