Developers

Every setlist, readable by machines.

Everything public on ryser.id is also available as data: the tracklist of a set, an artist and the sets they play in, a record and every set it was heard in. Two doors, one dataset.

REST APIRead tracklists in JSONSearch sets, fetch a timestamped tracklist, an artist's page or a record's versions. No key, 60 requests a minute per address, cached five minutes, any origin.API reference →MCP serverAsk your assistantChatGPT, Claude, Cursor and every MCP client can query ryser.id directly. Five tools, no key, Streamable HTTP at one URL.Connect an assistant →

Sixty seconds to a tracklist

No key, no account: ask for the tracklist of a set you know the link of.

bash
curl "https://ryser.id/api/public/search?url=https://www.youtube.com/watch?v=dQw4w9WgXcQ"

# found → { "found": true, "set": { "id": "…", "title": "…", "identified_tracks": 24, … } }
# not yet → 404 { "found": false, "analyse_url": "https://ryser.id/?url=…" }

curl https://ryser.id/api/public/sets/<set id>
# → the set with "tracks": [ { "start": "0:00", "artist": "…", "title": "…", "bpm": 128, "key": "8A", … } ]

Prefer talking to it? Add https://ryser.id/api/mcp as a connector in ChatGPT or Claude and ask for the tracklist by link. How to connect →

What is in the data

  • Sets. Public analyses: sets people ran and shared, and the library, sets ryser.id scans every day from the big channels. Each has an id, the source link, duration and a timestamped tracklist with status, tempo and key per row.
  • Artists. One canonical page per DJ or producer with their links, the tracks they are most played with, the sets they performed and the sets they were played in. Spelling variants resolve to the same artist.
  • Tracks. One canonical record with the versions heard (original, remix, edit) and every public set it appears in, with the timestamp.

Every object carries its public URL on ryser.id. Please link there when you show the data.

Fair use

  • Public data is free to read. Link back to the set, artist or track page you used.
  • Keep polling gentle. Responses are cached for five minutes, so asking more often returns the same answer.
  • Do not republish whole tracklists as your own database, and do not present ryser.id data as your own identification.
  • Stay under 60 requests a minute from one address. Over it you get a 429 until the next minute starts.

Building something?

Radio, festivals, agencies, labels, DJ tools: we offer higher limits, bulk exports and invoiced billing. Tell us what you are making and we will set you up. Small projects welcome too; a note is enough.

[email protected] →

Status: beta. Endpoints and field names are stable; fields may be added. Changes are announced on What’s new. Machine-readable summary at /llms.txt.