# Spotify — API Agent Score

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

Spotify scored 79/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 100/100 (A+)
- Developer Experience: 66/100 (C)
- Agent Discovery: 83/100 (A)
- Agent Understanding: 76/100 (B)
- Agent Usability: 69/100 (C)

## Check Results

### API Design

- [pass] Machine-readable, versioned contract — Versioning declared (info.version="1.0.0") and url-versioning detected. Investigated: spec 100%, docs 100%.
- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: spec 100%, docs 100%, wellknown 0%.
- [warn] Schema coverage & depth — 286/290 (99%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 100%, spec 67%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 50%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, spec 0%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Self-service signup at https://www.spotify.com/us/signup; no free tier or sandbox language detected. Investigated: docs 100%.
- [warn] Description completeness — 161/165 operations carry a description. Investigated: sdk 98%, spec 0%.
- [pass] Changelog published — Newest official SDK activity 45 day(s) ago. Investigated: sdk 100%, spec 0%, docs 0%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 2 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (darren-project/obsidian-spotify, 1 snippets). Investigated: docs 100%, sdk 100%, cli 0%, mcp 0%, wellknown 0%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 1 pages. Investigated: docs 80%, sdk 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/1 pages return markdown). Investigated: docs 75%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 5 distinct 4xx/5xx response codes documented. Investigated: docs 100%, sdk 100%, spec 50%.
- [pass] Operation purpose clarity — 94% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 75%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, docs) is 7% (threshold 35% for full credit).
- [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 2 assessed pages (2 JS-rendered). Investigated: docs 0%.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%, spec 0%, docs 0%.
- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%, spec 0%, docs 0%.
- [warn] Pagination documented & consistent — Only 22/32 list method(s) return an auto-paginating iterable; 10 return a raw page. Investigated: sdk 69%, spec 0%, docs 0%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.

## Executive Summary

Spotify's API program shows genuine strength in API design and agent discoverability, giving partners a solid structural foundation. However, two areas are holding back the partner experience: agents and AI coding tools lack the machine-readable context they need to understand and use the API confidently, and partners face friction getting to their first successful call — missing a quickstart and code samples slows onboarding from minutes to days. Prioritize publishing agent-readable context files and runnable collections first, then close the onboarding gap to compress the time from API discovery to a working integration.