Head to head · Music search · October 2026 research run
Slipstream vs The Rights Foundry
The Rights Foundry scores 53.3 (D) on agent readiness against Slipstream's 50 (D), and leads in 6 of 7 scored categories. Slipstream leads on reliability. Both do music search.
Best music and sound libraries for AI agents · All 21 music libraries comparisons
Which one, for what
Best for An agent helping a Slipstream subscriber find, clip and clear music for video, or an enterprise issuing rate-card licences with approval.
Ahead on
- Reliability, 80 against 30
Watch for
An initialize with no token answered 401 on 22 November 2026, so the catalogue tools the docs call public were not reachable without signing in
Best for An app or agent that places human-made music in video made inside a product and records a licence per sync.
Ahead on
- Schema & documentation, 80 against 50
- Agent ergonomics, 74 against 60
- Security & auth, 55 against 47
- Payments & pricing, 35 against 25
- Maintenance & community, 27 against 18
- Transparency & trust, 68 against 37
Watch for
Terms and licensing page describe the service as BETA, with access by invitation code and prices that may change
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reliability Slipstream +50
Slipstream 80
Atlassian Statuspage at status.slipstreammusic.com with Platform and API components and no MCP component (20). The history page and its RSS feed list no incidents, and the last 15 days each read no incidents reported (30). Partner quotas are daily and monthly with a burst limit per key, but the only numbers (1,000 a day, 30,000 a month) are an example usage block, and no limits are given for OAuth users (5 of 15). The licence endpoint returns 429 throttled with Retry-After and is safe to repeat for the same user, track and project, and async MCP tools are polled with identical arguments (15). No SLA found on the pages read; the main site could not be read (0). The MCP server and API carry no beta label (10). 20 + 30 + 5 + 15 + 0 + 10 = 80.
The Rights Foundry 30
Graded on the REST API. No status page found (0). No readable incident history (5). The only limit with a number is the MCP cap of 1,000 calls a UTC day. The docs say dashboard keys have no cap, while the terms say calls are rate limited without figures (10 of 15). 429 and billing 503 carry Retry-After, and each error status says whether it was charged, whether a refund is queued and when to retry. A sync link reissued within its window is free, and the docs warn to serialise concurrent first requests (15). No SLA (0). The terms, licensing page and calculator describe the service as BETA, with access by invitation code (0). 0 + 5 + 10 + 15 + 0 + 0 = 30.
Transparency & trust The Rights Foundry +31
Slipstream 37
Closed service. The licence coverage by plan, the banned uses and the rule that content published during a subscription stays covered after cancelling are set out in dated help centre articles, but the terms (a Notion page that rendered no text) could not be read (10 of 30). No privacy policy, DPA or retention statement was read (0 of 30). The changelog says breaking changes are announced ahead with migration steps, with no notice period and no dated notice read (8 of 20). No subprocessors or data locations found, beyond the docs' mention of S3 for downloads (0 of 20). 10 + 0 + 8 + 0 = 18.
The Rights Foundry 68
Closed service with clear terms (26 October 2026) and a licence page that sets out each licence type, its exclusions and that a sync lasts for the life of the content (15). The privacy policy (10 November 2026) gives a retention period for each kind of record, says customer content and assistant activity are not used to train models, and agrees with the terms. No DPA found (25 of 30). The terms give 30 days' notice to change or end BETA access and email notice of material changes. The retired search path answers 410 with a pointer and a date, but no deprecation policy for the API was found (12 of 20). Sub-processors and data locations are listed (Cloudflare, Neon (us-east-1), Stripe, Brevo, Google Analytics and Hugging Face) (20). 15 + 25 + 12 + 20 = 72.
Schema & documentation The Rights Foundry +30
Slipstream 50
The docs say tool inputs and outputs are typed, but tools/list could not be read because initialize answered 401, and the REST API has no OpenAPI file or other contract linked (10 of 25). No llms.txt (404) or Markdown docs for agents (0). The tools page states each tool's purpose and when to use it, for example soundtrack_a_video only when no video is attached and get_track_download_url as a download, not a licence (15 of 20). Filter values come from get_search_filters, audio_type takes three values and stems take separate id lists, but no schema was read (8 of 15). End-to-end flows for soundtracks, AudioVerify, allowlists and licences, and REST error tables with stable codes (12 of 15). REST paths are versioned (/api/v4/, /api/v1/) and a changelog page exists, but its entries load by script and its feeds answered 405 (5 of 15). 10 + 0 + 15 + 8 + 12 + 5 = 50.
The Rights Foundry 80
A public OpenAPI 3.1 file, version 1.0, covers all seven operations (25). No llms.txt (404 on the docs host) and no Markdown docs. The reference is one HTML page (0). Descriptions say when to use each search mode and when to use another, with a table choosing between them (20). Typed inputs with enums for vocals, sort and booleans, length and range limits, required fields, and a sync body that rejects unknown keys (15). Request and response examples for every operation, and every error status documented with its body (15). Versioned /v1/ paths and a dated retirement of /v1/tracks/creative-brief on 24 September 2026 in the reference, but no public changelog (5). The MCP tool definitions were not readable. 25 + 0 + 20 + 15 + 15 + 5 = 80.
Agent ergonomics The Rights Foundry +14
Slipstream 60
MCP reading. 56 tools with no toolsets, dynamic loading or read-only subset (5 of 25). Search takes genre, mood, vocals, BPM and duration filters, REST search takes limit and offset with next and previous links, and an over-tight filter stack is relaxed and reported in relaxed_filters (15 of 20). REST errors return success: false with a stable code and a message, and the MCP docs say a capped call returns a clear message, with already-added channels and videos returning success (15 of 20). The docs say every tool carries readOnlyHint, destructiveHint, idempotentHint and openWorldHint, licences are idempotent for the same user, track and project, and renders are polled with identical arguments, not verified in tools/list (18 of 20). Few required parameters, and six registered prompts, but no official SDK (7 of 15). 5 + 15 + 15 + 18 + 7 = 60.
The Rights Foundry 74
limit from 1 to 100 per page and per-request charging keep responses sized, but there is no field selection (15). Page and limit, tag, BPM, key, duration, vocals, decade and explicit filters, and sort fields (20). Errors name the cause, the fix and whether the call was charged, with constraints.empty_because naming the filter to loosen on an empty page (20). Free sync reissue within the paid window and best-effort refunds on server errors, but no idempotency key, and concurrent first syncs can both be charged (12). Few required parameters and sensible defaults, but no official SDK found, although the builders page lists JavaScript, Python and Swift SDKs (7). 15 + 20 + 20 + 12 + 7 = 74.
Payments & pricing The Rights Foundry +10
Slipstream 25
No x402, MPP or L402 (0). Individual ($120 a year) and Teams ($2,400 a year) plan prices are public in the help centre, Enterprise and MCP licence fees come from a negotiated rate card, and single-track prices are on a pricing page we couldn't read (15 of 30). The developer docs say a Free tier can connect, but the help centre's MCP guide asks for an active subscription, both trials need a card, downloads answer 403 for free accounts, and initialize answered 401 without a token (10 of 30). A person signs in through a browser, and partner tokens and keys come by contacting Slipstream (0). 0 + 15 + 10 + 0 = 25.
The Rights Foundry 35
No x402, MPP or L402 (0). Plan prices and credit allowances are public, and the calculator gives how many syncs, streams and AI searches each plan buys, so per-unit costs can be derived. The exact rate card is returned only by the authenticated GET /v1/credits, and the docs print no prices (20 of 30). A free Foundation tier of 1,000 credits a month and free beta credits for new accounts. No card step is described, but card use was not confirmed, the licensing page says BETA access is by invitation, and the terms say free access carries no commercial licence (15 of 30). A person signs up in a browser with an emailed code, and MCP OAuth needs a person to sign in and approve (0). 0 + 20 + 15 + 0 = 35.
Maintenance & community The Rights Foundry +9
Slipstream 18
Closed-service reading. No dated API or MCP change could be read because the changelog loads by script and its feeds answered 405. The newest dated page about the MCP is the help centre guide of 3 August 2026, within 180 days (10 of 30). Dated changelog entries in the last 90 days unchecked (0 of 20). A changelog page that promises advance notice of breaking changes, support by chat and support@slipstreammusic.com with a stated 24 to 48 hour reply (8 of 15). No entry in the official MCP registry, and no official SDK (0 of 15). No package to judge (0 of 10). 10 + 0 + 8 + 0 + 0 = 18.
The Rights Foundry 27
Closed service. The last dated API change found is the retirement of /v1/tracks/creative-brief on 24 September 2026, 59 days before this check (20). No changelog, so no three dated changes in the last 90 days (0). No public changelog. Support by form and support@therightsfoundry.com, where the support page says a person replies, usually within one business day (7 of 15). No entry in the official MCP registry and no official SDK found (0). No package to judge (0). The domain was registered on 6 March 2026, about eight and a half months ago. 20 + 0 + 7 + 0 + 0 = 27.
Score by category
| Category | Weight | Slipstream | The Rights Foundry | Edge |
|---|---|---|---|---|
| Reliability | 16% | 80 | 30 | Slipstream +50 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 50 | 80 | The Rights Foundry +30 |
| Agent ergonomics | 13% | 60 | 74 | The Rights Foundry +14 |
| Security & auth | 14% | 47 | 55 | The Rights Foundry +8 |
| Payments & pricing | 10% | 25 | 35 | The Rights Foundry +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 18 | 27 | The Rights Foundry +9 |
| Transparency & trust | 7% | 37 | 68 | The Rights Foundry +31 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 50/100 | D 53.3/100 |
Facts side by side
| Fact | Slipstream | The Rights Foundry |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | Slipstream Music | The Rights Foundry |
| Hosted endpoint | https://mcp.slipstreammusic.com/mcp | https://mcp.therightsfoundry.com/mcp |
| Transports | Streamable HTTP | Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | subscription | Freemium |
| Price for music search | not published | $0.069 per call |
| x402 | no | no |
| Tools exposed | 56 | 0 |
| Read-only variant documented | yes | no |
| llms.txt | no | no |
| Last release | none | 2026-09-24 |
| Terms last updated | couldn't be read | 2026-10-26 |
| Privacy policy last updated | no document linked | 2026-11-10 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | yes |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
Verdicts
Slipstream
The MCP server documents 56 tools for search, downloads, stems, video soundtracks, rights checks and enterprise licences, and its licence flow waits for the user to approve the fee. Every call we could make needed a signed-in subscriber or a partner token, the REST API takes partner keys only, and the terms and privacy policy could not be read.
The Rights Foundry
The REST API has a detailed OpenAPI 3.1 file, three search modes, typed errors with charge rules, and a sync licence that outlasts the account. The service is in beta with no status page, SLA, changelog or SDK, the MCP tools are not documented, and preview streams are due to be charged at a rate not yet published.
Before you call either
Slipstream
- Expect a 401 and a browser OAuth sign-in on the first call, even for search, and ask the user to sign in with an active Slipstream subscription
- Call
prepare_licenseuntil it returnsready: true, show the user the one-lineconfirm, and callgenerate_licenseonce with the same values after they agree, since it mints a contract number - Treat
get_track_download_urlas a download only, not a licence, and remember the link spends the partner's download quota when opened - Poll
create_track_clip,extend_trackandrender_soundtrackwith identical arguments untilready: true, and keep callingget_compliance_resultwhile AudioVerify returnstimeout - Take filter values from
get_search_filtersorget_sfx_filters, because unknown values are dropped and an empty match retries without filters, reported inrelaxed_filters
The Rights Foundry
- Call
GET /v1/creditsbefore any charged call and read prices fromcosts, since the docs print none - Fetch page 1 of a Deep Search once with
limitup to 100, then page forward. Every page 1 is charged again - Send
{"external_export": true}to/syncwhen the video leaves the product. The default licence covers in-app use only - Serialise sync calls for the same track, because two first requests at once can both be charged
- Send no
Authorizationheader to signed asset URLs, and store track IDs rather than URLs, which expire after one hour
Questions
Which is better for AI agents, Slipstream or The Rights Foundry?
The Rights Foundry scores 53.3 (D) on agent readiness against Slipstream's 50 (D), and leads in 6 of 7 scored categories. Slipstream leads on reliability.
Do Slipstream and The Rights Foundry need an API key?
Slipstream uses an OAuth sign-in. The Rights Foundry takes an API key or an OAuth sign-in.
Can an agent call Slipstream and The Rights Foundry without installing anything?
Yes. Slipstream has a hosted endpoint at https://mcp.slipstreammusic.com/mcp and The Rights Foundry at https://mcp.therightsfoundry.com/mcp.
Other comparisons with Slipstream or The Rights Foundry
- Artyfile Music Licensing vs Slipstream
- Artyfile Music Licensing vs The Rights Foundry
- Epidemic Sound MCP Server vs Slipstream
- Epidemic Sound MCP Server vs The Rights Foundry
- Free Music Library MCP vs Slipstream
- Free Music Library MCP vs The Rights Foundry
- Lots of Sounds vs Slipstream
- Lots of Sounds vs The Rights Foundry
- LGDA Autonomic Pacing Node vs Slipstream
- LGDA Autonomic Pacing Node vs The Rights Foundry
Machine-readable
- This page as Markdown
/compare/slipstream-vs-the-rights-foundry.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/slipstream.json·/api/v1/tools/the-rights-foundry.json - From a terminal
anchor compare slipstream the-rights-foundry(the CLI) - Over MCP
compare_tools {"a": "slipstream", "b": "the-rights-foundry"}at/mcp, no key