Skip to the content
  1. Docs
  2. Billing and usage

Billing and usage

Core + Managed TransfersGuide · 2 min
What one billed request is, how MusicAPI Core and MusicAPI Managed Transfers are metered, the price tiers per 1,000 requests, the €500 monthly minimum, and where to see your usage.

MusicAPI bills by the request, in euros, once a month. There is no seat price and no per-user price.

What one request is

The meter counts one request for each of these:

WhatCounts as
A library call: /api/{integrationUserUUID}/…One request, failed calls included
A sign-in that connects an account (hosted sign-in or a pre-authorized session)One request
A call that a managed transfer makes to a music serviceOne request per call. Retries of one call do not count again.

Not billed:

  • the Match Results API;
  • anything on Demoify and the Sample library;
  • the docs sandbox.

Calls from a signed-in docs session count like any other call of your account.

Core and Managed Transfers metering

A managed transfer reads the source service and writes the destination service. Your plan decides which side is billed:

PlanTransfer requests billed
MusicAPI Managed TransfersBoth sides: the source reads and the destination writes
MusicAPI CoreThe source side only

The destination is your own service, so on the Core plan the writes into it are not billed. Your library calls and sign-ins are billed on both plans.

As a guide, one transfer makes about 60 requests on the source side and about 120 on the destination side. The real number depends on the size of the library and on the services.

Price per 1,000 requests

The tiers are cumulative within one month: the first 5 million requests are billed at the first rate, the next 20 million at the second, everything above at the third.

Monthly requestsPrice per 1,000 requests
0 – 5M€0.60
5M – 25M€0.45
25M +€0.30

The monthly minimum

Each month bills the greater of the metered charge and the €500 minimum. When the metered charge is lower, the invoice adds a "Minimum monthly spend top-up" line.

Requests in the monthMetered chargeInvoice
400,000400 × €0.60 = €240€500 (with a €260 top-up)
2,000,0002,000 × €0.60 = €1,200€1,200
8,000,0005,000 × €0.60 + 3,000 × €0.45 = €4,350€4,350

The pricing page has a calculator.

Where to see usage

  • Analytics → API usage in the dashboard: requests over time, by endpoint, error rates and response times.
  • The MCP server tool get_usage_summary: the billed requests of this month and last month, from the same table as the invoices. The numbers lag a few hours.

Invoices

Invoices come from Stripe, by default once a month. A different cycle, a custom tier or a custom limit is part of your agreement with us. Contact us.

Keep the bill down

  • Store what you read. A playlist list does not change every second.
  • Use limitParam with the service's maximum, so a full read takes fewer pages.
  • Send at most 20 items per write, but do send 20, not one at a time.
  • Use webhooks instead of polling.