# LGDA Autonomic Pacing Node vs Slipstream

> LGDA Autonomic Pacing Node scores 51.1 (D) to Slipstream's 50 (D) for music license. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/lgda-autonomic-node-vs-slipstream
- Markdown: https://www.anchorterminal.com/compare/lgda-autonomic-node-vs-slipstream.md (~4,850 tokens)
- Slim: https://www.anchorterminal.com/compare/lgda-autonomic-node-vs-slipstream.min.md (~1,130 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/lgda-autonomic-node-vs-slipstream.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-22

LGDA Autonomic Pacing Node scores 51.1 (D) on agent readiness against Slipstream's 50 (D), and leads in 4 of 7 scored categories. Slipstream leads on reliability, security & auth and transparency & trust. Both do music license. LGDA Autonomic Pacing Node accepts x402. Slipstream doesn't.

- LGDA Autonomic Pacing Node: grade D, 51.1/100, rank #1143 of 1571. Markdown https://www.anchorterminal.com/tools/lgda-autonomic-node.md · JSON https://www.anchorterminal.com/api/v1/tools/lgda-autonomic-node.json
- Slipstream: grade D, 50/100, rank #1174 of 1571. Markdown https://www.anchorterminal.com/tools/slipstream.md · JSON https://www.anchorterminal.com/api/v1/tools/slipstream.json
- Best music and sound libraries for AI agents: https://www.anchorterminal.com/best/music-libraries/index.md
- All 21 music libraries comparisons: https://www.anchorterminal.com/compare/music-libraries/index.md

## Which one, for what

### LGDA Autonomic Pacing Node (D)

Good for: A small wellness music catalogue for an agent that plays music during a person's own relaxation or biometric session.

Ahead on:
- Schema & documentation, 64 against 50
- Agent ergonomics, 66 against 60
- Payments & pricing, 85 against 25
- Maintenance & community, 72 against 18

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

### Slipstream (D)

Good 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 22
- Security & auth, 47 against 39
- Transparency & trust, 37 against 21

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


## Why the edge

### 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.
- 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.

### Reliability: Slipstream +58

- 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.
- 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.

### Maintenance & community: LGDA Autonomic Pacing Node +54

- 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.
- 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.

### Transparency & trust: Slipstream +16

- 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.
- 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.

### Schema & documentation: LGDA Autonomic Pacing Node +14

- 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.
- 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.

### Security & auth: Slipstream +8

- 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.
- Slipstream (47): OAuth 2.1 with PKCE and dynamic client registration, but a single `mcp` scope, and partner REST keys carry scopes such as `licenses:generate` with revoked and expired states (25 of 30). Licences need a read-only `prepare_license` step and the user's approval of the fee before `generate_license`, the docs say tools carry destructive hints, and pricing comes from the caller's own rate card so a caller can't name its fee, but OAuth gives no read-only mode (12 of 20). Results include public playlist names and descriptions written by other users and track lookups from outside links, with no prompt-injection guidance found (5 of 15). Each client shows in the Slipstream admin and can be revoked, and partner responses report usage, with no per-call log found (5 of 15). No security.txt on the developer host and no disclosure policy, bug bounty or certification found; the main site could not be read (0 of 20). 25 + 12 + 5 + 5 + 0 = 47.

## Score by category

| Category | Weight | LGDA Autonomic Pacing Node | Slipstream | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 22 | 80 | Slipstream +58 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 64 | 50 | LGDA Autonomic Pacing Node +14 |
| Agent ergonomics | 13% | 66 | 60 | LGDA Autonomic Pacing Node +6 |
| Security & auth | 14% | 39 | 47 | Slipstream +8 |
| Payments & pricing | 10% | 85 | 25 | LGDA Autonomic Pacing Node +60 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 72 | 18 | LGDA Autonomic Pacing Node +54 |
| Transparency & trust | 7% | 21 | 37 | Slipstream +16 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **51.1 · D** | **50 · D** | |

## Facts side by side

| Fact | LGDA Autonomic Pacing Node | Slipstream |
| --- | --- | --- |
| Kind | MCP server | MCP server |
| Vendor | LGDA Technologies | Slipstream Music |
| Hosted endpoint | `https://lgda-music.fly.dev/mcp` | `https://mcp.slipstreammusic.com/mcp` |
| Transports | Streamable HTTP | Streamable HTTP |
| Auth | None | OAuth |
| Pricing | Pay per use | subscription |
| x402 | yes, from $5.99/call | no |
| Licence | MIT | none |
| Tools exposed | 6 | 56 |
| Read-only variant documented | no | yes |
| llms.txt | no | no |
| MCP registry | `io.github.lgda-technologies/lgda-autonomic-node` | not listed |
| Last release | 2026-11-20 | none |
| Terms last updated | no document linked | couldn't be read |
| Privacy policy last updated | no document linked | no document linked |
| Customer content may train models | not read yet | couldn't be read |
| Terms restrict automated access | not read yet | couldn't be read |
| Terms restrict benchmarking | not read yet | couldn't be read |
| Terms or service can change without notice | not read yet | couldn't be read |
| Arbitration or class-action waiver | not read yet | couldn't be read |

## 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.

**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.

## 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

### Slipstream

1. 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
2. Call `prepare_license` until it returns `ready: true`, show the user the one-line `confirm`, and call `generate_license` once with the same values after they agree, since it mints a contract number
3. Treat `get_track_download_url` as a download only, not a licence, and remember the link spends the partner's download quota when opened
4. Poll `create_track_clip`, `extend_track` and `render_soundtrack` with identical arguments until `ready: true`, and keep calling `get_compliance_result` while AudioVerify returns `timeout`
5. Take filter values from `get_search_filters` or `get_sfx_filters`, because unknown values are dropped and an empty match retries without filters, reported in `relaxed_filters`

## Questions

### Which is better for AI agents, LGDA Autonomic Pacing Node or Slipstream?

LGDA Autonomic Pacing Node scores 51.1 (D) on agent readiness against Slipstream's 50 (D), and leads in 4 of 7 scored categories. Slipstream leads on reliability, security & auth and transparency & trust.

### Do LGDA Autonomic Pacing Node and Slipstream need an API key?

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

Yes. LGDA Autonomic Pacing Node has a hosted endpoint at https://lgda-music.fly.dev/mcp and Slipstream at https://mcp.slipstreammusic.com/mcp.

### Are LGDA Autonomic Pacing Node and Slipstream open source?

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


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/lgda-autonomic-node-vs-slipstream.json, and with the fewest tokens: https://www.anchorterminal.com/compare/lgda-autonomic-node-vs-slipstream.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "lgda-autonomic-node", "b": "slipstream"}`. From a terminal: `anchor compare lgda-autonomic-node slipstream`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/lgda-autonomic-node.json and https://www.anchorterminal.com/api/v1/tools/slipstream.json

## Other comparisons with LGDA Autonomic Pacing Node or Slipstream

- [Artyfile Music Licensing vs Slipstream](https://www.anchorterminal.com/compare/artyfile-vs-slipstream.md)
- [Epidemic Sound MCP Server vs Slipstream](https://www.anchorterminal.com/compare/epidemic-sound-vs-slipstream.md)
- [Free Music Library MCP vs Slipstream](https://www.anchorterminal.com/compare/free-music-library-mcp-vs-slipstream.md)
- [Lots of Sounds vs Slipstream](https://www.anchorterminal.com/compare/lotsofsounds-vs-slipstream.md)
- [Slipstream vs The Rights Foundry](https://www.anchorterminal.com/compare/slipstream-vs-the-rights-foundry.md)
- [Artyfile Music Licensing vs LGDA Autonomic Pacing Node](https://www.anchorterminal.com/compare/artyfile-vs-lgda-autonomic-node.md)
- [Epidemic Sound MCP Server vs LGDA Autonomic Pacing Node](https://www.anchorterminal.com/compare/epidemic-sound-vs-lgda-autonomic-node.md)
- [LGDA Autonomic Pacing Node vs The Rights Foundry](https://www.anchorterminal.com/compare/lgda-autonomic-node-vs-the-rights-foundry.md)
- [Free Music Library MCP vs LGDA Autonomic Pacing Node](https://www.anchorterminal.com/compare/free-music-library-mcp-vs-lgda-autonomic-node.md)
- [LGDA Autonomic Pacing Node vs Lots of Sounds](https://www.anchorterminal.com/compare/lgda-autonomic-node-vs-lotsofsounds.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
