Talk to your royalties. Build on them too.
Connect Royalti to Claude, Claude Code or Cursor in minutes — or build directly against the REST API. Same royalty data, your choice of interface.
$ claude mcp add --transport http royalti \ https://api.royalti.io/ai/mcp # then run /mcp and sign in with your Royalti account ✓ royalti connected — 80 tools > Which artists earned the most last quarter? ⏺ getRoyaltyByArtist · Q1 2026 (sample) 1. ████████ ▇▇▇▇▇▇ 2. ██████ ▇▇▇▇▇ 3. █████ ▇▇▇▇
- 80
- MCP tools
- 900+
- REST endpoints
- 9
- tool domains
- 20
- currencies
Your royalty platform, inside your AI assistant
Royalti's MCP server gives Claude, Claude Code and Cursor direct, permissioned access to your catalog, royalties, splits, and analytics. Ask in plain language; get answers from your real data.
- "Which artists earned the most last quarter?"royalties
- "Which royalty statements failed to process, and why?"files
- "Audit metadata across the catalog before Friday's delivery."catalog · files
9 pre-built prompts ship with the server — revenue forecasts, metadata audits, split configuration, and more.
Read the setup guide →{
"mcpServers": {
"royalti": {
"url": "https://api.royalti.io/ai/mcp",
"headers": { "Authorization": "Bearer RWAK_…" }
}
}
}- ·automations
- ·catalog
- ·files
- ·payments
- ·publishing
- ·releases
- ·royalties
- ·search
- ·splits
900+ endpoints. Every royalty workflow.
// 1 — authenticate, 2 — scope to your workspace
const login = await fetch('https://api.royalti.io/auth/login', {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({ email, password }),
}).then(r => r.json());
const { token } = await fetch(
'https://api.royalti.io/auth/authtoken?currentWorkspace=ws_0001',
{ headers: { Authorization: `Bearer ${login.token}` } }
).then(r => r.json());
// 3 — query your catalog (page-based pagination)
const artists = await fetch(
'https://api.royalti.io/artists?page=1&size=25',
{ headers: { Authorization: `Bearer ${token}` } }
).then(r => r.json());# authenticate → scope to a workspace → query your catalog
curl -X POST https://api.royalti.io/auth/login \
-H 'Content-Type: application/json' \
-d '{"email":"you@label.com","password":"…"}'
curl 'https://api.royalti.io/auth/authtoken?currentWorkspace=ws_0001' \
-H "Authorization: Bearer $LOGIN_TOKEN"
curl 'https://api.royalti.io/artists?page=1&size=25' \
-H "Authorization: Bearer $WORKSPACE_TOKEN"Auth, catalog, splits, royalties, accounting, payments, publishing — plus webhooks and real-time events for long-running work.
- auth
- JWT (6h access / 1d refresh) · workspace + user API keys · OAuth: Google, LinkedIn, Facebook
- pagination
- page-based — page, size (max 100), sort, order
- webhooks
- HMAC-signed, per-event subscriptions
- real-time
- Socket.IO events for file processing + workflows
- status
- status.royalti.io
The whole platform is addressable
Royalty processing
Ingest statements from 30+ distributor formats; AI column mapping handles the rest.
Catalog + splits
Artists, releases, tracks — and advanced splits: temporal, conditional, succession, bulk CSV.
Analytics
9 dimensions, 7 chart types, BigQuery-powered at catalog scale.
Payments + billing
20 currencies, Stripe usage-based billing, member payment flows.
Publishing + CWR
Works, writers, agreements, registrations — live in production since June 2026.
DDEX deliveryevery paid plan
ERN/MEAD generation and DSP delivery to Spotify, Apple Music, and more — included with every paid plan.
Scoped keys on a hosted endpoint
Scoped, revocable keys
Workspace keys (RWAK_) and user keys (RUAK_) — scoped to a tenant, revocable from the dashboard.
Scopes set the tool list
A key with only ai:tools:read sees 41 tools. A key with all four AI scopes, or full access, sees all 80.
Hosted endpoint
mcp.royalti.io with per-tenant isolation, structured audit logging, and rate limiting on upstream calls.
Quick answers
Which AI clients work with the MCP server?
Clients that support remote HTTP MCP servers, such as Claude, Claude Code and Cursor.
Are DDEX delivery tools included in my plan?
DDEX delivery (ERN/MEAD) is included with every paid plan — there's nothing separate to buy. Every other tool domain ships with every workspace.
How do I authenticate against the REST API?
JWT sessions (6-hour access, 1-day refresh) or workspace API keys; OAuth sign-in via Google, LinkedIn, or Facebook.
Where's the full API reference?
apidocs.royalti.io — every endpoint, request/response shapes, and integration guides.
Do I have to run the MCP server myself?
No. Royalti hosts the MCP server at mcp.royalti.io, so there is nothing to install or run. Point your MCP client at https://api.royalti.io/ai/mcp and sign in with your Royalti account (OAuth), or send a Royalti API key in the Authorization header. Scopes on the key set what the server lists: a key with only ai:tools:read sees 41 tools, and a key with ai:chat, ai:tools:read, ai:tools:write and ai:tools:payments:read (or full access) sees all 80.
Point your AI at your royalty data
Grab a workspace API key from your dashboard and connect your first client today.