Pricing

Pricing That Scales With Your Catalog

Three tiers for PROs and publishers at every stage of adoption. Start with a pilot segment, expand to full production volume when you are ready.

Pilot

$499

per month

For PROs and publishers evaluating the attribution model. Index a catalog segment and run attribution queries at a manageable volume to assess fit before scaling.

  • 5,000 track identifications per month
  • Attribution API access
  • JSON response with catalog matches and confidence scores
  • Rights holder identifier mapping
  • Royalty weighting recommendations
  • Email support and API documentation
Request Pilot Access

Network

Custom

volume pricing, contact us

For network-level PROs and major publisher groups with multi-catalog environments, custom SLAs, and multi-jurisdiction rights routing requirements.

  • Unlimited track identifications
  • All Publisher features
  • White-label attribution reports
  • Dedicated account manager
  • SLA with uptime guarantee
  • Multi-jurisdiction rights routing
Contact Us

Early Access

Request API Access

Musical AI is currently in early access for qualifying performing rights organizations and music publishers. Submit your details and we will be in touch within 3 business days.

Questions before applying? Email us at [email protected]

FAQ

Common Questions

One identification is one call to the POST /v1/attribute endpoint. The count does not vary based on how many matches are returned or the duration of the submitted audio (up to the 10-minute limit per call).
Musical AI is currently in early access. The Pilot tier is specifically designed for evaluation: index a catalog segment and run attribution queries before deciding whether to scale up. Apply via the form below and we will follow up within 3 business days.
The Publisher plan includes a dedicated batch endpoint that accepts multiple audio URLs in a single request and processes them asynchronously. Webhook notifications fire when each job completes, so your workflow does not need to poll for status. Each track in a batch counts as one identification toward your monthly total.
Yes. Each organization's catalog is stored in a logically isolated namespace. Cross-client data access is architecturally prevented at the storage layer. Your catalog data is used only to serve your own attribution queries and is never used for model training or cross-client analysis.
Each response includes a ranked array of catalog matches. For each match: the ISRC, a confidence score from 0.0 to 1.0, the rights-holder identifier from your catalog, the stem type that produced the match (e.g. vocal_lead, harmonic, percussion), and the royalty weighting recommendation. Publisher and Network plans include the full audit trail export in JSON and CSV formats.