Head to head · Music download · October 2026 research run

LGDA Autonomic Pacing Node vs Lots of Sounds

Lots of Sounds scores 52.9 (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 download. LGDA Autonomic Pacing Node accepts x402. Lots of Sounds doesn't.

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

Which one, for what

LGDA Autonomic Pacing Node D

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 25
  • Maintenance & community, 72 against 66

Also in its favour

  • An agent can pay per call over x402, with no account
  • No key needed to call it
  • Open source
  • No incidents deducted, where Lots of Sounds loses 3 points for them

Watch for

Each purchase is licensed for personal sessions only, so the tracks cannot be used in videos, games, adverts, broadcast or model training

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 22
  • Schema & documentation, 79 against 64
  • Agent ergonomics, 88 against 66
  • Security & auth, 46 against 39
  • Transparency & trust, 43 against 21

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

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 +60

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.

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.

Agent ergonomics Lots of Sounds +22

LGDA Autonomic Pacing Node 66

Six compact tools, 4,305 characters for the whole tools/list answer (25). No pagination, filtering or search. list_catalog returns the whole catalogue of 27 tracks with evidence, which is small, and get_track_evidence narrows to one track (6 of 20). Errors name the unknown track or album, and the README documents what each HTTP status on /stream and /play means (13 of 20). All six tools carry readOnlyHint, destructiveHint and idempotentHint, with the three paid tools marked not idempotent. A purchase returns a signed session token that lets an agent download an entitled track again without paying. No idempotency key on payments (15 of 20). Two required arguments on each paid tool and none on the catalogue. No SDK in any language, only an agent skill in a second repository that was not read (7 of 15). 25+6+13+15+7 = 66.

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.

Transparency & trust Lots of Sounds +22

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.

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.

Reliability Lots of Sounds +18

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.

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.

Schema & documentation Lots of Sounds +15

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.

Lots of Sounds 79

Public OpenAPI 3.1 spec with 7 operations, and typed JSON Schema inputs on all 5 MCP tools, read with one tools/list (25). llms.txt and llms-full.txt, plus a Copy Markdown option on each docs page (10). Tool descriptions say how search matches, when to call download_sound and that get_profile is only for identifying the account, with fewer when-not-to-use lines in the spec (14 of 20). Enums for category, sort and order, minimum and maximum on limit and page, required ids, and additionalProperties: false on every tool. Duration filters have no bounds (13 of 15). Examples in curl, JavaScript and Python and an error table with actions, but the spec's error schema is a single error string and the coded errors (plan_required, rate_limited) are documented for the CLI only (12 of 15). Paths are versioned /api/v1 and the spec is 1.0.0, but the one dated changelog post is from March 2026 (5 of 15). The spec says 12,000+ sounds where llms.txt says 16,874, and tags use OR on the sample endpoint and AND on search. 25 + 10 + 14 + 13 + 12 + 5 = 79.

Security & auth Lots of Sounds +7

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.

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.

Score by category

CategoryWeightLGDA Autonomic Pacing NodeLots of SoundsEdge
Reliability16%2240Lots of Sounds +18
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6479Lots of Sounds +15
Agent ergonomics13%6688Lots of Sounds +22
Security & auth14%3946Lots of Sounds +7
Payments & pricing10%8525LGDA Autonomic Pacing Node +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7266LGDA Autonomic Pacing Node +6
Transparency & trust7%2143Lots of Sounds +22
Negative events≤150-3
TotalD 51.1/100D 52.9/100

Facts side by side

FactLGDA Autonomic Pacing NodeLots of Sounds
KindMCP serverMCP server
VendorLGDA TechnologiesLots of Sounds (Elliott Labs)
Hosted endpointhttps://lgda-music.fly.dev/mcphttps://api.lotsofsounds.com/mcp
TransportsStreamable HTTPStreamable HTTP
AuthNoneOAuth or key
PricingPay per useFreemium
x402yes, from $5.99/callno
LicenceMITnone
Tools exposed65
Read-only variant documentednoyes
llms.txtnoyes
MCP registryio.github.lgda-technologies/lgda-autonomic-nodecom.lotsofsounds/mcp
Last release2026-11-202026-10-29
Terms last updatedno document linked2026-04-01
Privacy policy last updatedno document linked2026-10-19
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetnot 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.

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.

Before you call either

LGDA Autonomic Pacing Node

  1. Get your user's approval before calling purchase_track, purchase_album or play_track_session, because a payment moves USDC with no server-side check
  2. Use a purchased track only in sessions for the user it was bought for, and never in published, commercial or training work
  3. Keep the X-LGDA-Session token from a purchase, and present it to /stream to download each entitled track again without paying
  4. Call list_catalog first to get track and album slugs, because the id fields take free strings with no enum
  5. Treat per-track RMSSD and heart-rate figures as vendor claims from 24 sessions, not evidence of a health effect

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

Questions

Which is better for AI agents, LGDA Autonomic Pacing Node or Lots of Sounds?

Lots of Sounds scores 52.9 (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 Lots of Sounds need an API key?

LGDA Autonomic Pacing Node needs no key. Lots of Sounds 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 Lots of Sounds without installing anything?

Yes. LGDA Autonomic Pacing Node has a hosted endpoint at https://lgda-music.fly.dev/mcp and Lots of Sounds at https://api.lotsofsounds.com/mcp.

Are LGDA Autonomic Pacing Node and Lots of Sounds open source?

LGDA Autonomic Pacing Node is open source (MIT). No open-source release is listed for Lots of Sounds.

Other comparisons with LGDA Autonomic Pacing Node or Lots of Sounds

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.