◎ Discry Score
spotify.com
communication · API
B
0 / 100
DISCOVERY0
COMPREHENSION0
Category leader: 98 (A)
Discry your API →
COMMUNICATION · RANK #14 OF 24

Spotify is Good to agents.

Discry independently scored how well an AI agent can discover and understand the Spotify API from what’s public — not whether it’s usable. Below: every signal we checked, what’s costing the score, and what to change.

Discry your API — freeView the docs ↗

SCORED UNDER RUBRIC 1.2 · A full re-launch under Discry Score 2.5 — a new behavioral instrument, not comparable to these scores — is in progress.

Discovery

45% of score · 67/100
OpenAPI specA machine-readable OpenAPI/Swagger spec agents can parse.Pass
llms.txtAn llms.txt index that points agents to the docs that matter.Pass
llms.txt qualityThe llms.txt is focused, current, and well under the size budget.Pass
llms-full.txtA full-text bundle agents can load in one request.Fail
AGENTS.mdAn AGENTS.md that tells coding agents how to build on the API.Fail
.well-known/mcp.jsonA discoverable MCP manifest at a well-known path.Fail
MCP registryThe API is listed in a public MCP registry.Pass
robots.txt AI directivesrobots.txt allows (or explicitly guides) AI crawlers.Pass
SitemapA sitemap so agents can enumerate the docs surface.Fail

Comprehension

55% of score · 88/100
Task-oriented descriptionsEndpoints described by what they accomplish, not just their shape.Pass
Realistic examplesRunnable, real-world request/response examples.Partial
Multi-step workflowsDocs that chain calls into complete jobs an agent can follow.Pass
Error-recovery guidanceDocumented failure modes and how to recover from them.Partial
Answer-first formatThe answer leads; preamble does not bury it.Pass
Capability boundariesClear limits — what the API can and cannot do.Pass
Naming consistencyConsistent, predictable naming across endpoints.Pass
Heading hierarchyClean heading structure agents can navigate.Pass
Markdown docsDocs available as clean markdown, not JS-rendered HTML only.Pass
Token efficiencyDocs are concise enough to fit an agent context window.Pass

What we found

  • Spotify provides a concise, well-structured llms.txt (668 bytes) that links directly to the OpenAPI spec and a Building with AI tutorial — exemplary agent discovery
  • The OpenAPI 3.0 spec is publicly accessible at /reference/web-api/open-api-schema.yaml and explicitly allowed in robots.txt
  • An agent would find multiple community MCP servers on PulseMCP and Glama for playback control and catalog search
  • Documentation includes a dedicated Building with AI tutorial showing how to integrate with AI coding assistants
  • Sitemap returns a 404 page-not-found HTML response, hurting standard web crawler discovery

What to change

Prioritized by impact on discoverability. You (or your docs platform) deploy these — Discry never touches your API.

  1. 01Add llms-full.txt with comprehensive API documentation in markdown
  2. 02Fix sitemap.xml to return valid XML with documentation pages listed
  3. 03Add AGENTS.md to the spotify GitHub org with context for coding agents
  4. 04Add .well-known/mcp.json pointing to community or official MCP server
  5. 05Include more realistic code examples with actual values across multiple languages

Execution coverage · INFORMATIONAL, UNSCORED

Whether an agent can actually complete a call and recover from errors is the deeper Audit layer — documented here, but not part of the Discry Score.

OAuth2✓ Error format documented✓ Rate limits documented✓ Pagination documented✕ Idempotency documented

Spotify uses OAuth 2.0 (authorization code, client credentials, PKCE). JSON error responses. Rate limits documented with quota modes. Cursor-based pagination. No idempotency keys documented.

See your own Discry Score.

Drop your API docs URL. See what an agent sees — in 60 seconds, free.

Discry your API — free