← Back to leaderboard
Vercel API
61
C
Vercel scores a C with strong semantics (92) and intent (87) but zero examples — none of the 304 operations or 69 schemas include them. The spec also still carries version `0.0.1`, suggesting it's machine-generated and not actively curated. Error handling and pagination are better than most competitors, but the missing examples force agents to guess at request shape every time.
Category breakdown
Examples0
Semantics92
Intent87
Error Handling67
Parameters80
Pagination45
Key findings
- All 304 operations and 69 schemas lack examples
- 217 of 1,073 parameters lack descriptions
- 16 list operations lack pagination parameters
- 20 operations have missing or poor operationIds
What Vercel should fix
- Add at least one example per operation. Vercel's deployment objects, env vars, and project configs have specific shapes that examples make instantly clear.
- Bump the spec version. `0.0.1` signals to AI agents (and humans) that the spec isn't treated as production-quality documentation.
- Add pagination parameters to the 16 list operations missing them — particularly deployments and logs, where agents frequently need to iterate.
- Fix the 20 weak operationIds.
How does your API score?
Run AgenticScore on your own OpenAPI spec — find issues before LLMs do.
npx agenticscore score ./openapi.yaml
Get API Key →