API and MCP: tracklists for your tools
By Ryan Poser, who builds ryser.idUpdated First published
The short answer
Everything public on ryser.id can be read by machines, free and without a key: a REST API at /api/public that returns JSON (60 requests a minute per address), and an MCP server at https://ryser.id/api/mcp that ChatGPT, Claude and other assistants can connect to. Both cover public sets, artists and tracks; neither scans a new set.
In short
- REST
- GET /api/public/... returns JSON. No key, any origin, cached five minutes, 60 requests a minute per address.
- MCP
- https://ryser.id/api/mcp, Streamable HTTP, no authentication for public data.
- What you can read
- Public sets and their tracklists, artists and tracks. A set nobody analysed is not in the data.
- Docs
- API reference and MCP setup per assistant.
Everything public on ryser.id is also readable by machines: the tracklist of a set, an artist's page, a track's versions and appearances. There are two doors. This guide is the short version; the full reference lives at /developers/api and the per-client setup for assistants at /developers/mcp.
MCP for ChatGPT, Claude and other assistants
ryser.id runs an MCP server at https://ryser.id/api/mcp (Streamable HTTP, no authentication for public data). Add it as a connector or remote MCP server in your assistant, then ask things like "what is the tracklist of this Boiler Room set?" with the YouTube link, or "which sets played Kelaya by Da Capo?".
Tools it exposes:
search_dj_sets(query): sets by DJ, event, channel or title.get_tracklist(set_id or url): the timestamped tracklist of a public set.get_artist(slug): links, most played tracks, sets performed and played in.get_track(slug): versions heard and every set it appears in.latest_sets(origin): the newest public tracklists, library or community.
REST for scripts
No key and no account needed: call the endpoints as they are. All of them return JSON, allow any origin, are cached for five minutes and allow 60 requests per minute per address. A key sent from before is simply ignored.
GET https://ryser.id/api/public/search?q=cercle
GET https://ryser.id/api/public/search?url=https://www.youtube.com/watch?v=...
GET https://ryser.id/api/public/search?latest=library&limit=20
GET https://ryser.id/api/public/sets/<set id>
GET https://ryser.id/api/public/artists/black-coffee
GET https://ryser.id/api/public/tracks/da-capo-kelaya
The browser extension endpoint GET /api/public/tracklist?url=<set link> returns a compact tracklist for the page someone is on.
A set has id, title, uploader, source_url, duration_seconds, identified_tracks, origin (library for the daily automatic scans, community for sets people analysed and shared) and, on the set endpoint, tracks with start, artist, title, status, bpm, key and links.
A set nobody has analysed yet is not in the data. The search answers with a link where anyone can analyse it on ryser.id.
Fair use
Public data is free to read. Please link back to the set, artist or track page you used, keep polling gentle (the cache is five minutes anyway), and do not republish whole tracklists as your own database. If you build something on it, tell us: [email protected].
Questions
Is there a 1001Tracklists API?
1001Tracklists offers no public API for reading tracklists. ryser.id's own tracklists can be read as JSON without a key, or through MCP from an assistant: see the API reference.
Do I need an API key?
No. The public endpoints answer without a key or an account. A key sent from before is ignored.
Can I start a new analysis through the API?
No. The API and the MCP server read what is public. To identify a new set, paste its link on ryser.id.
Got a set link? Get its tracklist.
Paste the link and ryser.id names every track it can, with the time it starts. No account? The quick peek under the box does the first 30 minutes for free and mails you the list.
Other guides
Getting started with ryser.id: your first tracklistPaste a set link or upload a recording and get every track it can name, with times, BPM and key. With or without an account, what it costs, how to check the result and what to do with it.Updated 16 October 2026
Reading the setlist: the marks, the rows and checking every trackWhat Proven, Found, Weak, To check and Unknown mean, what each part of a row does on a phone and a computer, how Check every track works, and how to fix a track.Updated 14 October 2026
Minutes, plans and passes: what ryser.id costsEvery set finishes, and you only pay for what we find. Every account gets free minutes each month; plans add hours, paid by the month or once for life, and packs add minutes that never expire. What each plan gives, how the pass works, refunds and switching.Updated 16 October 2026