Head to head · Music search · October 2026 research run

Artyfile Music Licensing vs The Rights Foundry

Artyfile Music Licensing scores 54.8 (C) on agent readiness against The Rights Foundry's 53.3 (D), and leads in 3 of 7 scored categories. The Rights Foundry leads on schema & documentation, agent ergonomics, security & auth and transparency & trust. Both do music search.

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

Which one, for what

Artyfile Music Licensing C

Best for An agent producing a video, ad or podcast that needs one or a few licensed recordings with a perpetual licence and a certificate, with the user on hand to pay.

Ahead on

  • Reliability, 40 against 30
  • Payments & pricing, 70 against 35

Also in its favour

  • No key needed to call it

Watch for

The same checkout sells Limited Edition master shares with royalty payouts, promoted on an "Invest in Music Royalties" page that says capital is at risk

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

  • Schema & documentation, 80 against 75
  • Agent ergonomics, 74 against 66
  • Security & auth, 55 against 43
  • Transparency & trust, 68 against 57

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 Artyfile Music Licensing +35

Artyfile Music Licensing 70

No x402, MPP or L402; checkout is a Stripe hosted page (0 of 10). €29.90 per track for Basic and €69.90 per 1% share, published without login on the pricing page, the spec and llms.txt (30). Search, licence terms and watermarked previews are free with no account or card, but no licence or full WAV is free (10 of 30). An agent reaches every endpoint with no signup or key (30). 0 + 30 + 10 + 30 = 70. A person still approves each purchase, which this checklist doesn't score.

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

Artyfile Music Licensing 43

No credential at all. Anyone can search and open a checkout, and the order publicId alone opens status, the WAV, the invoice and the certificate (15 of 30). The API reads the catalogue and can only create a checkout, and every payment needs a person to approve it on Stripe's page (18 of 20). Results carry titles and metadata from Artyfile and the artists it distributes, with no injection guidance (7 of 15). Each purchase yields an invoice and licence certificate, with no per-call log for the operator (3 of 15). No security.txt (404), disclosure policy, bug bounty or certification found (0 of 20). 15 + 18 + 7 + 3 + 0 = 43.

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.

Transparency & trust The Rights Foundry +11

Artyfile Music Licensing 57

Closed service with a dated licence agreement and terms, version 9 October 2026, that set the licence's scope, territory, duration and restrictions (15 of 30). The privacy policy of 19 November 2026 names the controller with its company number, retention by purpose and every processor. It says the agent interfaces are read-only and expose catalogue data only, while the spec's checkout creates orders and returns download and invoice links, and retention periods are often 'a short period' (15 of 30). The terms give 30 days' notice of material changes and keep existing licences on their original terms, with no API deprecation policy (5 of 20). Processors and their regions are named: Vercel, Neon and Upstash in Frankfurt, Cloudflare R2 in the EU, Stripe, Anthropic, OpenAI, Postmark and Google (20). 15 + 15 + 5 + 20 = 55.

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.

Reliability Artyfile Music Licensing +10

Artyfile Music Licensing 40

Graded on the REST API in the OpenAPI spec. No status page found on the site or in its sitemap (0). No readable incident history (5). Rate limits published per endpoint, 300 searches, 10 checkouts and 300 order reads an hour per IP (15). Each limit answers 429, but no Retry-After or backoff guidance is documented, while checkout takes an Idempotency-Key that replays the original session (10 of 15). No SLA (0). Version 1.0.0 with no beta label (10). 0 + 5 + 15 + 10 + 0 + 10 = 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.

Agent ergonomics The Rights Foundry +8

Artyfile Music Licensing 66

API reading of the checklist, since the MCP server was closed to our reader. Search results are sized with limit from 1 to 60, with no field selection (15 of 25). Filters for genre, mood, tempo and instrument, and no page or cursor parameter (12 of 20). Errors name the cause (product_not_found, basic_unavailable, le_capacity with availablePct, not_paid, wav_pending), and 429 carries no retry time (14 of 20). Checkout takes an Idempotency-Key and the other calls are GETs, while MCP readOnlyHint and destructiveHint annotations are unchecked (18 of 20). One required field on checkout and sensible defaults, with no official SDK (7 of 15). 15 + 12 + 14 + 18 + 7 = 66.

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.

Schema & documentation The Rights Foundry +5

Artyfile Music Licensing 75

Public OpenAPI 3.1 spec, Artyfile Agent API 1.0.0, read once because robots.txt allows /api/openapi.json (25). llms.txt has a section for agents that walks through the buy loop (10). The spec says what each step is for and when not to use it, such as skipping master_only Cover Editions and handing the Stripe URL to a person (15 of 20). Enums for tier, scope, locale and order status, bounds on limit and shares, and a required productId, but genre, mood, tempo and instrument are free strings with no listed values (10 of 15). Named error codes for 402, 404 and 409 and a 202 for a pending WAV, with no request examples in the spec and none for 400 (10 of 15). Versioned 1.0.0 with no public changelog (5 of 15). 25 + 10 + 15 + 10 + 10 + 5 = 75. The MCP tool definitions were not read.

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.

Score by category

CategoryWeightArtyfile Music LicensingThe Rights FoundryEdge
Reliability16%4030Artyfile Music Licensing +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7580The Rights Foundry +5
Agent ergonomics13%6674The Rights Foundry +8
Security & auth14%4355The Rights Foundry +12
Payments & pricing10%7035Artyfile Music Licensing +35
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3027Artyfile Music Licensing +3
Transparency & trust7%5768The Rights Foundry +11
Negative events≤1500
TotalC 54.8/100D 53.3/100

Facts side by side

FactArtyfile Music LicensingThe Rights Foundry
KindHTTP APIHTTP API
VendorArtyfileThe Rights Foundry
Hosted endpointhttps://artyfile.com/api/mcphttps://mcp.therightsfoundry.com/mcp
TransportsStreamable HTTPStreamable HTTP
AuthNoneOAuth or key
PricingPaidFreemium
Price for music searchnot published$0.069 per call
x402nono
Tools exposed60
Read-only variant documentednono
llms.txtyesno
MCP registrycom.artyfile/music-licensingnot listed
Last release2026-08-052026-09-24
Terms last updatedno date given2026-10-26
Privacy policy last updated2026-11-192026-11-10
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesyes
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

Artyfile Music Licensing

Artyfile lets an agent search 1,000+ recordings, read structured licence terms and prepare a €29.90 perpetual sync licence with no key, while a person approves every Stripe payment. There is no status page, changelog or security contact, and the same checkout sells royalty-paying master shares marketed as an investment.

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

Artyfile Music Licensing

  1. Skip results with licenseScope: "master_only" for any media project, because Cover Editions carry no sync licence
  2. Send an Idempotency-Key header on POST /api/checkout/basic, then show the returned Stripe url to the user, who must approve it within one hour
  3. Poll GET /api/order/{publicId} about every 15 seconds until status is paid, and retry the download later if wavPending is true
  4. Keep tier set to basic unless the user asks for a Limited Edition share, since le buys royalty-paying ownership, not only a licence
  5. Treat the publicId as a secret, because anyone holding it can fetch the WAV, invoice and certificate

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, Artyfile Music Licensing or The Rights Foundry?

Artyfile Music Licensing scores 54.8 (C) on agent readiness against The Rights Foundry's 53.3 (D), and leads in 3 of 7 scored categories. The Rights Foundry leads on schema & documentation, agent ergonomics, security & auth and transparency & trust.

Do Artyfile Music Licensing and The Rights Foundry need an API key?

Artyfile Music Licensing needs no key. The Rights Foundry takes an API key or an OAuth sign-in.

Can an agent call Artyfile Music Licensing and The Rights Foundry without installing anything?

Yes. Artyfile Music Licensing has a hosted endpoint at https://artyfile.com/api/mcp and The Rights Foundry at https://mcp.therightsfoundry.com/mcp.

Other comparisons with Artyfile Music Licensing 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.