WAYS IN
Four ways into the same workspace.
The same catalog, statements and splits, whichever way you reach them. Every figure still opens back to its line.
| WHERE YOU WORK | WHAT IT’S FOR | GETTING YOUR DATA IN | HOW TO START |
|---|---|---|---|
| In the app | Load statements, match lines to your catalog, set splits, pay people. Everything, with nothing to install. | Drop statements and catalog sheets. A layout we don’t know yet is mapped once in the Source Creator. | app.royalti.ioStart free |
| Ask Roy | Ask about your own data in plain words, inside the app: what is on a statement, which lines matched a work, what is still unmatched. | Roy reads what’s in the workspace. Drop a statement file into the chat and it starts the import; you check the mapping. | Example questionWhich lines on our Q2 BMI statement didn’t match a work?See Roy |
| From your AI tool | Connects to MCP clients that support remote HTTP servers, such as Claude, Claude Code and Cursor. Sign in with your Royalti account, or use an API key. Skills teach it the royalty work. | Hand it a folder of exports: it sets up artists, releases and splits, loads the statements through the API, and tells you what didn’t match. | claude mcp add --transport http royalti \
https://api.royalti.io/ai/mcp
npx skills add royalti-io/royalti-skillsThen run /mcp and sign in with your Royalti account. For an API key, add --header "Authorization: Bearer RWAK_…" to the first line.Connect your AI tool |
| From your own systems | The REST API, for imports, nightly syncs and your own reports. | Push statements and catalog from the system you run today, on a schedule, with the same checks as a manual upload. | POST api.royalti.io/file/upload-url
POST api.royalti.io/file/confirm-upload-completionRead the API docs |
It’s how we onboard new workspaces ourselves: a folder of exports, an AI tool connected to the workspace, and a person checking what it flags.
Keys are per workspace. Create and delete them in Settings.FROM YOUR AI TOOL
Hand it a folder of exports. Check what it did.
Royalti connects to MCP clients that support remote HTTP servers, such as Claude, Claude Code and Cursor. Sign in with your Royalti account, or use an API key. Every step your tool takes is a line you can read.
- 1Sign in, or create a keySign in with your Royalti account when your tool asks. Or create an API key in Settings, then API keys, and delete it whenever you like.
- 2Connect your tool
claude mcp add --transport http royalti \ https://api.royalti.io/ai/mcpThen run /mcp and sign in with your Royalti account. Using an API key instead? Add --header "Authorization: Bearer RWAK_…" to the same line. - 3Add the Royalti skills
npx skills add royalti-io/royalti-skillsOpen source on GitHub: the app, CWR registration and DDEX skills. The API skill is listed in the same catalog.
A SESSION, AS IT RANLAGOON RECORDS · SAMPLE
PROMPTHere are our 2025 DistroKid statements and our catalog sheet. Set up the artists and releases, load the four quarters, and tell me what didn’t match.
MCPuploadGuidanceWhich template DistroKid statements use×1
MCPcreateArtistFrom the catalog sheet×12
MCPcreateProductReleases, with UPCs×31
MCPcreateAssetTracks, with ISRCs×146
MCPcreateDefaultSplitsArtist 50%, label 50%, from the sheet×146
APIPOST /file/upload-urlOne per quarter, through the API skill×4
APIPOST /file/confirm-upload-completionStarts processing×4
MCPgetFileStatusUntil all four finished×4
MCPsearchAssetsByISRCThe ISRCs that didn’t match×3
Done. 12 artists, 31 releases and 146 tracks set up. 1,842 statement lines loaded; 1,812 matched a track.FLAG30 lines carry 3 ISRCs that aren’t in your catalog sheet
PICK A WAY IN