GitHub API

https://github.com · v1.1.4 · 1186 operations · 929 schemas

GitHub's 1,186-operation spec scores 55, a D. Examples and error documentation are middling, but two categories drag the score down hard. Pagination scores 4 out of 100. Parameter descriptions score 9. For the largest API in this study, that means agents have almost no way to reliably page through resources, and almost no context on what each parameter expects. Most agent calls into GitHub will work the first time, then misbehave in ways that are hard to debug.

Category breakdown

Examples57

Semantics88

Intent33

Error Handling54

Parameters9

Pagination4

Key findings

All 1,186 operations have missing or machine-generated operationIds
916 of 929 schemas lack examples
Most parameters lack descriptions
Most list operations lack pagination parameters
388 of 929 schemas have no description

What GitHub should fix

Replace machine-generated operationIds with human-readable verbs that match the documentation (`listOrganizationRepositories` not `repos/list-for-org`).
Document parameters across all operations. "limit", "page", "since" are not self-explanatory at the scale of 1,000+ endpoints.
Add explicit pagination metadata (next/prev links or cursor parameters) to the list operations missing it.
Add examples to the 916 schemas without them. With nearly 1,000 schemas, agents need anchors.

How does your API score?

Run AgenticScore on your own OpenAPI spec — find issues before LLMs do.

npx agenticscore score ./openapi.yaml

Install the CLI →