Head to head · Music license · October 2026 research run
LGDA Autonomic Pacing Node vs The Rights Foundry
The Rights Foundry scores 53.3 (D) on agent readiness against LGDA Autonomic Pacing Node's 51.1 (D), and leads in 5 of 7 scored categories. LGDA Autonomic Pacing Node leads on payments & pricing and maintenance & community. Both do music license. LGDA Autonomic Pacing Node accepts x402. The Rights Foundry doesn't.
Best music and sound libraries for AI agents · All 21 music libraries comparisons
Which one, for what
Best for A small wellness music catalogue for an agent that plays music during a person's own relaxation or biometric session.
Ahead on
- Payments & pricing, 85 against 35
- Maintenance & community, 72 against 27
Also in its favour
- An agent can pay per call over x402, with no account
- No key needed to call it
- Open source
Watch for
Each purchase is licensed for personal sessions only, so the tracks cannot be used in videos, games, adverts, broadcast or model training
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
- Reliability, 30 against 22
- Schema & documentation, 80 against 64
- Agent ergonomics, 74 against 66
- Security & auth, 55 against 39
- Transparency & trust, 68 against 21
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.
Payments & pricing LGDA Autonomic Pacing Node +50
LGDA Autonomic Pacing Node 85
x402 v1 and v2 on the vendor's own node for every paid item, 36 purchase resources and 27 play resources on Base mainnet in USDC (10). Prices of $5.99 a track, $14.99 an album and $0.05 a play are published in the manifest and README without a login (30). The catalogue and per-track evidence are free to read with no account, but no free play or sample was found. BeliefState took 15 for free discovery calls in the same position (15 of 30). An agent with a funded Base wallet buys with no account, key or signup (30). 10+30+15+30 = 85.
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.
Transparency & trust The Rights Foundry +47
LGDA Autonomic Pacing Node 21
The editorial half. The server code is MIT, and the LICENSE says it covers the code only. The music is licensed per purchase under the README's terms, which are clear on what a buyer may and may not do. There are no separate terms of service (25 of 30). No privacy policy was found, though verify_session takes heart-rate variability readings. The code read signs a receipt and does not store the readings, but what the hosting keeps isn't stated (3 of 30). No deprecation policy. Version 1 at lgda-node.fly.dev was left running, and the README says the owner cannot reach its account (0 of 20). The README and fly.toml name Fly.io in region iad, the x402.org facilitator and Base44 for the storefront and files, with no subprocessor list (8 of 20). 25+3+0+8 = 36. The provenance half is computed from the provenance block.
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.
Maintenance & community LGDA Autonomic Pacing Node +45
LGDA Autonomic Pacing Node 72
Read as a hosted service with public source. The latest release is 2.5.0 in the MCP registry on 20 November 2026 (30). Six registry versions from 17 to 20 November 2026 (20). github.com refused our reader, so issues and pull requests were not read. No support channel or community was found beyond the storefront's Contact page, whose content a script draws and which was not read (3 of 25). Listed in the official MCP registry under the GitHub-verified namespace io.github.lgda-technologies (15). Four runtime dependencies with version ranges and 43 tests in the repository, with no CI workflow (4 of 10). 30+20+3+15+4 = 72. The repository has 21 commits from 17 to 21 November 2026, so the server is five days old.
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.
Schema & documentation The Rights Foundry +16
LGDA Autonomic Pacing Node 64
Typed JSON Schema inputs on all six tools, with additionalProperties: false, but the pre and post fields of verify_session are untyped objects (23 of 25). No llms.txt (/llms.txt answered 404). The README is Markdown in the repository but nothing is served for agents beyond the manifest (0). Descriptions state purpose, price and the next step, and play_track_session says to use purchase_track to own a track instead. No when-not-to-use guidance on the others (14 of 20). Required fields are set and session_id has a pattern and a length limit, but track_id and album_id take free strings with no enum of the 27 slugs (8 of 15). One example slug per id field, and the README lists the 400, 402, 404 and 503 answers of /stream and /play. JSON-RPC errors carry -32602 and a message (9 of 15). Semver releases in the registry and a per-version account in the README and the code's header, with no dated changelog file and no git tags (10 of 15). An OpenAPI page at /docs is linked from the node's home page and was not read. 23+0+14+8+9+10 = 64.
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.
Security & auth The Rights Foundry +16
LGDA Autonomic Pacing Node 39
There is no credential to leak. Each payment is an EIP-3009 authorisation for the exact amount to one stated wallet, but there are no accounts, keys, scopes or revocation, so the agent's wallet is the only control (15 of 30). The three paid tools are annotated as writes and the two catalogue tools as read-only, but nothing on the server asks a person to approve a purchase, and the README says there is no human in the loop (8 of 20). Responses are the vendor's own catalogue and evidence and the agent's own submitted values. No third-party text reaches the agent (10 of 15). Each settled payment returns a settlement header with the transaction hash, purchases leave an on-chain record, and receipts are Ed25519-signed. No operator log or dashboard (6 of 15). No security.txt checked, no SECURITY.md, disclosure policy, bug bounty or certification found (0 of 20). 15+8+10+6+0 = 39.
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.
Reliability The Rights Foundry +8
LGDA Autonomic Pacing Node 22
Read with the hosted lines, on the MCP server at lgda-music.fly.dev. No status page found, only a /healthz that reported version 2.5.0, 27 of 27 audio files loaded and the Base network on 22 November 2026 (0). No incident history to read (5). No rate limits found in the README, the code or the manifest (0). The code and README document the payment order, verify then check the track can be delivered then settle, so a payment for an unknown track or missing audio is never settled and the payer can retry with corrected parameters. No 429 or Retry-After handling found (7 of 15). No SLA (0). No beta or preview label on the server or its tools (10). 0+5+0+7+0+10 = 22.
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.
Score by category
| Category | Weight | LGDA Autonomic Pacing Node | The Rights Foundry | Edge |
|---|---|---|---|---|
| Reliability | 16% | 22 | 30 | The Rights Foundry +8 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 64 | 80 | The Rights Foundry +16 |
| Agent ergonomics | 13% | 66 | 74 | The Rights Foundry +8 |
| Security & auth | 14% | 39 | 55 | The Rights Foundry +16 |
| Payments & pricing | 10% | 85 | 35 | LGDA Autonomic Pacing Node +50 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 72 | 27 | LGDA Autonomic Pacing Node +45 |
| Transparency & trust | 7% | 21 | 68 | The Rights Foundry +47 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 51.1/100 | D 53.3/100 |
Facts side by side
| Fact | LGDA Autonomic Pacing Node | The Rights Foundry |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | LGDA Technologies | The Rights Foundry |
| Hosted endpoint | https://lgda-music.fly.dev/mcp | https://mcp.therightsfoundry.com/mcp |
| Transports | Streamable HTTP | Streamable HTTP |
| Auth | None | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | yes, from $5.99/call | no |
| Licence | MIT | none |
| Tools exposed | 6 | 0 |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| MCP registry | io.github.lgda-technologies/lgda-autonomic-node | not listed |
| Last release | 2026-11-20 | 2026-09-24 |
| Terms last updated | no document linked | 2026-10-26 |
| Privacy policy last updated | no document linked | 2026-11-10 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | yes |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
Verdicts
LGDA Autonomic Pacing Node
An agent with a funded Base wallet can buy a track for $5.99, an album for $14.99 or one play for $0.05 over x402, with no account. Each purchase allows personal session use only. Payments go to one wallet with no approval step, the operator is unidentified, and the server is five days old with no privacy policy.
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
LGDA Autonomic Pacing Node
- Get your user's approval before calling
purchase_track,purchase_albumorplay_track_session, because a payment moves USDC with no server-side check - Use a purchased track only in sessions for the user it was bought for, and never in published, commercial or training work
- Keep the
X-LGDA-Sessiontoken from a purchase, and present it to/streamto download each entitled track again without paying - Call
list_catalogfirst to get track and album slugs, because the id fields take free strings with no enum - Treat per-track RMSSD and heart-rate figures as vendor claims from 24 sessions, not evidence of a health effect
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, LGDA Autonomic Pacing Node or The Rights Foundry?
The Rights Foundry scores 53.3 (D) on agent readiness against LGDA Autonomic Pacing Node's 51.1 (D), and leads in 5 of 7 scored categories. LGDA Autonomic Pacing Node leads on payments & pricing and maintenance & community.
Do LGDA Autonomic Pacing Node and The Rights Foundry need an API key?
LGDA Autonomic Pacing Node needs no key. The Rights Foundry takes an API key or an OAuth sign-in. An agent can also pay LGDA Autonomic Pacing Node per call over x402, with no account.
Can an agent call LGDA Autonomic Pacing Node and The Rights Foundry without installing anything?
Yes. LGDA Autonomic Pacing Node has a hosted endpoint at https://lgda-music.fly.dev/mcp and The Rights Foundry at https://mcp.therightsfoundry.com/mcp.
Are LGDA Autonomic Pacing Node and The Rights Foundry open source?
LGDA Autonomic Pacing Node is open source (MIT). No open-source release is listed for The Rights Foundry.
Other comparisons with LGDA Autonomic Pacing Node or The Rights Foundry
- Artyfile Music Licensing vs The Rights Foundry
- Epidemic Sound MCP Server vs The Rights Foundry
- Free Music Library MCP vs The Rights Foundry
- Lots of Sounds vs The Rights Foundry
- Slipstream vs The Rights Foundry
- Artyfile Music Licensing vs LGDA Autonomic Pacing Node
- Epidemic Sound MCP Server vs LGDA Autonomic Pacing Node
- LGDA Autonomic Pacing Node vs Slipstream
- Free Music Library MCP vs LGDA Autonomic Pacing Node
- LGDA Autonomic Pacing Node vs Lots of Sounds
Machine-readable
- This page as Markdown
/compare/lgda-autonomic-node-vs-the-rights-foundry.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/lgda-autonomic-node.json·/api/v1/tools/the-rights-foundry.json - From a terminal
anchor compare lgda-autonomic-node the-rights-foundry(the CLI) - Over MCP
compare_tools {"a": "lgda-autonomic-node", "b": "the-rights-foundry"}at/mcp, no key