API and MCP: tracklists for your tools

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

Create a free API key under Account (any account, no plan needed) and send it as Authorization: Bearer rysk_…. All endpoints return JSON, allow any origin, are cached for five minutes and allow 60 requests per minute per key.

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> stays keyless.

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.

Starting a scan from code

Analysing a new set costs minutes from your account and needs an API key. Create one under Account, then:

POST https://ryser.id/api/v1/runs
Authorization: Bearer <your key>
{ "url": "https://soundcloud.com/..." }

GET /api/v1/runs lists your runs; GET /api/v1/runs/<id> returns one with its tracklist.

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].