Head to head · Music search · October 2026 research run

Lots of Sounds vs The Rights Foundry

The Rights Foundry and Lots of Sounds score within a point of each other on agent readiness, 53.3 (D) and 52.9 (D). Lots of Sounds leads on reliability, agent ergonomics and maintenance & community. Both do music search.

Best music and sound libraries for AI agents · All 21 music libraries comparisons

Which one, for what

Lots of Sounds D

Best for An agent that needs short CC0 sound effects, ambience or loops with trim points and loudness for video, apps or games.

Ahead on

  • Reliability, 40 against 30
  • Agent ergonomics, 88 against 74
  • Maintenance & community, 66 against 27

Watch for

No page says where the CC0 sounds come from or who recorded them, and the licence page leaves checking suitability to the user

The Rights Foundry D

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

  • Security & auth, 55 against 46
  • Payments & pricing, 35 against 25
  • Transparency & trust, 68 against 43

Also in its favour

  • No incidents deducted, where Lots of Sounds loses 3 points for them

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.

Maintenance & community Lots of Sounds +39

Lots of Sounds 66

Closed service. The npm CLI 0.1.0 was published on 29 October 2026, 24 days ago (30). In the last 90 days the examples repository changed on 26 August and 21 September, the registry entry and TypeScript client appeared on 21 September, the privacy policy took effect on 19 October and the CLI shipped on 29 October, but none of these is a dated changelog entry (10 of 20). The blog's only changelog is March 2026, the roadmap lists a shipped MCP server as in progress, and support is team@lotsofsounds.com with a reply within one business day stated on the pricing page and a UserJot feedback board (6 of 15, closed-service reading). Listed in the official MCP registry as com.lotsofsounds/mcp, a reverse-DNS namespace on its own domain (15). The CLI has no install scripts and the TypeScript client has CI, but the CLI's source repository named on npm isn't public (5 of 10). 30 + 10 + 6 + 15 + 5 = 66.

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.

Transparency & trust The Rights Foundry +25

Lots of Sounds 43

Closed service with terms of 1 April 2026 and a licence page that put every sound under CC0 1.0. No page read says where the sounds come from, who recorded them or how their CC0 status was checked. Sound ids carry an fs- prefix, sound pages show added dates from 2017, and the roadmap plans generated sounds, so the licence's basis can't be traced (10 of 30). The privacy policy of 19 October 2026 lists what is collected, including search terms, and says data is kept 'as long as reasonably necessary', with no periods, DPA or deletion route beyond an email (10 of 30). No deprecation policy or dated notices (0 of 20). Processors are named by type only (hosting, authentication, payments), with no list or locations (3 of 20). 10 + 10 + 0 + 3 = 23.

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.

Agent ergonomics Lots of Sounds +14

Lots of Sounds 88

Five compact tools, about 5,000 characters of definitions (25). Search takes page and limit (up to 100), category, tags, duration bounds and sort, and returns total and totalPages (20). Errors are documented with a status, a meaning and an action, and 429 carries a reset time, though MCP error shapes were not seen because no tool was called (15 of 20). Every tool carries readOnlyHint, destructiveHint and idempotentHint, the reads are idempotent, and download_sound is marked non-destructive (20). Defaults on every optional parameter and one required field at most. The npm CLI and examples in JavaScript and Python exist, but the TypeScript client was not found on npm, so there is one published package (8 of 15). 25 + 20 + 15 + 20 + 8 = 88.

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.

Reliability Lots of Sounds +10

Lots of Sounds 40

Graded on the hosted MCP server and the REST API beneath it. No status page found, only the words 'API status: operational' on the home page with no link (0). No readable incident history (5). Daily limits published with numbers, 2,500 for Pro and 50,000 for Enterprise, resetting at midnight UTC (15). The API reference documents 429 with X-RateLimit-Reset and asks for bounded exponential backoff on 429 and 5xx, and every call is a read (15). The home page claims a 99.9% uptime SLA, but the terms of 1 April 2026 say the service is as-is and availability isn't guaranteed, and no SLA document was found (0). Nothing is labelled beta and the registry entry is version 1.0.0, but the public roadmap still lists the MCP server as in progress (5 of 10). 0 + 5 + 15 + 15 + 0 + 5 = 40.

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.

Payments & pricing The Rights Foundry +10

Lots of Sounds 25

No x402, MPP or L402 (0). Plan prices are public without login, Pro $15 and Enterprise $49 a month, with no per-call price (15). The free plan needs no card but has no API access. Twelve curated samples answer with no key through browse_samples and /api/v1/sounds/sample, which shows the response shape and nothing more (5 of 30). Full access needs a person to sign up and subscribe in a browser, and the CLI's device-code login also needs a person to approve. The keyless sample tool earns a little (5 of 30). 0 + 15 + 5 + 5 = 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.

Security & auth The Rights Foundry +9

Lots of Sounds 46

A plain API key in the x-api-key header, up to 2 on Pro and 20 on Enterprise, made in the dashboard. No scopes, expiry or rotation were documented. The OpenAI endpoint uses OAuth through clerk.lotsofsounds.com with identity scopes only (openid, profile, email), and no key travels in a query string (20 of 30). The whole surface is read-only, with nothing to delete or buy through the API (15 of 20). Results carry catalogue names, descriptions and tags written by the service, with no injection guidance found (8 of 15). Rate limit headers on each response and a statement in the privacy policy that API and MCP use is logged, with no per-call log for the operator found (3 of 15). security.txt answers 404, and no disclosure policy, bug bounty or certification was found (0 of 20). 20 + 15 + 8 + 3 + 0 = 46.

The Rights Foundry 55

Dashboard tokens are plain bearer keys that never expire and are revoked from the dashboard. MCP connections use OAuth 2.1 with PKCE and a 30-day expiry, but a single catalog:read scope (22 of 30). No read-only key and no per-purchase approval found. The privacy policy says a connected assistant can license tracks and spend credits, and only the vendor can switch sync off per token (5 of 20). Results are catalogue metadata curated by the vendor, and Acoustic Similarity Search fetches a URL the caller supplies, with no injection guidance found (8 of 15). The dashboard shows usage, credit balance, connected assistants and 30 days of sync reports, and each response carries X-Request-Id (12 of 15). Valid security.txt and a disclosure policy with response times and safe harbour, with no bug bounty or certification found (8 of 20). 22 + 5 + 8 + 12 + 8 = 55.

Score by category

CategoryWeightLots of SoundsThe Rights FoundryEdge
Reliability16%4030Lots of Sounds +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7980The Rights Foundry +1
Agent ergonomics13%8874Lots of Sounds +14
Security & auth14%4655The Rights Foundry +9
Payments & pricing10%2535The Rights Foundry +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6627Lots of Sounds +39
Transparency & trust7%4368The Rights Foundry +25
Negative events≤15-30
TotalD 52.9/100D 53.3/100

Facts side by side

FactLots of SoundsThe Rights Foundry
KindMCP serverHTTP API
VendorLots of Sounds (Elliott Labs)The Rights Foundry
Hosted endpointhttps://api.lotsofsounds.com/mcphttps://mcp.therightsfoundry.com/mcp
TransportsStreamable HTTPStreamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
Price for music searchnot published$0.069 per call
x402nono
Tools exposed50
Read-only variant documentedyesno
llms.txtyesno
MCP registrycom.lotsofsounds/mcpnot listed
Last release2026-10-292026-09-24
Terms last updated2026-04-012026-10-26
Privacy policy last updated2026-10-192026-11-10
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text

Verdicts

Lots of Sounds

A small, read-only MCP server and REST API with typed inputs, tool annotations, numbered daily limits and timing and loudness data on each sound. API access needs a person to sign up and subscribe, no page says where the CC0 sounds come from, and the home page's brand logos and uptime SLA have nothing behind them.

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

Lots of Sounds

  1. Send short keywords in q, because every word must match a name, description or tag and search isn't semantic
  2. Call download_sound only when the user is ready, because the signed URL expires after one hour
  3. If the server returns 429, wait for X-RateLimit-Reset, which falls at midnight UTC for the daily limit
  4. Pass one or two tags on search_sounds, since tags match with AND logic there and with OR logic on the sample endpoint
  5. Tell the user the source of each sound isn't stated before they use it in a product where provenance matters

The Rights Foundry

  1. Call GET /v1/credits before any charged call and read prices from costs, since the docs print none
  2. Fetch page 1 of a Deep Search once with limit up to 100, then page forward. Every page 1 is charged again
  3. Send {"external_export": true} to /sync when the video leaves the product. The default licence covers in-app use only
  4. Serialise sync calls for the same track, because two first requests at once can both be charged
  5. Send no Authorization header to signed asset URLs, and store track IDs rather than URLs, which expire after one hour

Questions

Which is better for AI agents, Lots of Sounds or The Rights Foundry?

The Rights Foundry and Lots of Sounds score within a point of each other on agent readiness, 53.3 (D) and 52.9 (D). Lots of Sounds leads on reliability, agent ergonomics and maintenance & community.

Do Lots of Sounds and The Rights Foundry need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Lots of Sounds and The Rights Foundry without installing anything?

Yes. Lots of Sounds has a hosted endpoint at https://api.lotsofsounds.com/mcp and The Rights Foundry at https://mcp.therightsfoundry.com/mcp.

Other comparisons with Lots of Sounds or The Rights Foundry

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.