10 minTime to key
NoNo-human path
4Human gates
6/10Onboarding score
CAPTCHACard before first callEmail verificationManual review
Fastest path to a key
- Email verificationCreate Spotify account (email verification) and hold an ACTIVE Premium subscription (required for app owners of Development Mode apps since Feb 2026).
- Log in at developer.spotify.com/dashboard -> accept Developer Terms.
- Create app: name, description, redirect URI, tick 'Web API' -> Save -> copy Client ID / Client Secret (limit 1 client ID per developer for new apps).
- client_credentials token (public catalog) or Authorization Code + PKCE (user data) -> first call. Dev mode: max 5 users, many endpoints removed, search capped at 10 results.
- Consumer agent path: add Spotify connector https://mcp-gateway-external-pilot.spotify.net/mcp in Claude/ChatGPT -> OAuth via accounts.spotify.com.
- Working API key
Biggest gap
Feb 2026 dev-mode restrictions (Premium required, 5 users, 1 client ID) and no DCR, so custom agents cannot use the MCP gateway.
Worth copying
robots.txt explicitly allows the OpenAPI spec while blocking other YAMLs; a dedicated 'Building with AI' guide.
Sources (10) · checked 2026-10-11
- https://developer.spotify.com/llms.txt
- https://developer.spotify.com/documentation/web-api/tutorials/building-with-ai
- https://developer.spotify.com/documentation/web-api/tutorials/february-2026-migration-guide
- https://developer.spotify.com/robots.txt
- https://www.spotify.com/robots.txt
- https://mcp-gateway-external-pilot.spotify.net/mcp (probed: 401 w/ PRM)
- https://mcp-gateway-external-pilot.spotify.net/.well-known/oauth-protected-resource
- https://accounts.spotify.com/.well-known/oauth-authorization-server
- https://accounts.spotify.com/.well-known/openid-configuration
- https://claude.com/marketplace/connectors/spotify
35Readiness score / 100
L1 Agent-readableBeats 46% of 1,846 companies
Access16/20
Context11/20
Interfaces8/32
Onboarding0/19
Trust0/9
llms.txt · docs
Biggest gains
- +12 Remote MCP server for the product. Host a remote MCP server (e.g. mcp.<domain>/mcp, Streamable HTTP) for your core actions.
- +8 Machine-readable API spec. Publish an OpenAPI spec at a stable URL like /openapi.json and link it from llms.txt.
- +6 Docs available as markdown. Serve every docs page as .md, or honour Accept: text/markdown.
All 20 checks
- PASSAgents get the real page, not a bot wall10
- PASSrobots.txt lets user-triggered agents in6
- FAILContent is server-rendered4
- PASSllms.txt exists8
- FAILllms-full.txt exists3
- FAILDocs available as markdown6
- PASSSitemap2
- PASSStructured metadata1
- PASSPublic developer docs4
- FAILMachine-readable API spec8
- FAILRemote MCP server for the product12
- FAILDocs MCP or searchable docs4
- PASSSDKs and a CLI4
- FAILOAuth discovery metadata5
- FAILAgents can self-register OAuth clients6
- FAILSelf-serve API keys5
- FAILFree tier or test mode3
- FAILAgent manifests4
- FAILsecurity.txt2
- FAILPublic status page3
Your fix pack: 14 changes, up to +65 points
Each change is ready to paste, filled in for spotify.com, with a command to check it worked. Or hand the whole list to your coding agent.
Add the badge to your README
[](https://agentsready.dev/c/spotify.com)