Skip to main content
MusicAPIv3
Pricing

You pay per request.
Nothing else.

One meter: requests we make to music streaming services on your behalf. No per-seat fee, no per-user fee, no charge for transfers that fail to match. Volume discounts apply automatically as buckets fill.

€0.60
per 1,000 — first 5M requests
€0.30
floor rate above 25M
€500
minimum monthly spend
0
per-seat or per-user fees
01 · Rate card

Three buckets, billed monthly.

Buckets are cumulative within a calendar month. Your first five million requests bill at the top rate, the next twenty million at the middle rate, and everything beyond at the floor.

Bucket 10 – 5M
0.60/ 1,000 requests
Where most integrations start. Covers a few hundred thousand library transfers a month.
bucket size5M requests
bucket at full€3,000
Bucket 25M – 25M
0.45/ 1,000 requests
A 25% step down, applied automatically the moment bucket 1 fills.
bucket size20M requests
bucket at full€9,000
Bucket 325M +
0.30/ 1,000 requests
Half the entry rate. Everything above 25M in the month bills here, with no cap.
bucket sizeunlimited
bucket at full
€500
Minimum monthly spend
Every account bills at least €500 per month. Below roughly 833,333 requests the minimum is what you pay — above it, you simply pay the meter.
€0
Not metered
Authentication redirects, dashboard seats, webhooks, sandbox traffic and support. Only requests that leave us for a music service are counted.
02 · What counts as a request

Core meters one side. Switch meters both.

The difference is who talks to the destination. With Core that's you, against your own platform, so we never see it. With Switch we run the whole transfer, source and destination — so both sides are on the meter.

★ Cheaper to run
COREsource requests only

You own the destination

SOURCE · BILLED
Spotify, Tidal, Deezer…
DESTINATION · FREE
Your own platform
Only requests we send to the source service are metered
Writes into your own catalogue happen on your infrastructure — invisible to billing
Roughly half the metered volume of the same transfer on Switch
SWITCHsource + destination requests

We run both sides

SOURCE · BILLED
Spotify, Tidal, Deezer…
DESTINATION · BILLED
Your service, via us
Source reads and destination writes both count as requests
Nothing to build or host on your side — the flow, retries and support are ours
Budget around 2× the request volume of the equivalent Core integration
03 · Estimate

Work out your month.

Set your expected monthly transfers. We model a typical listener at around 2,000 songs — roughly 60 source requests to read their library, plus about 120 destination requests if we're writing it too.

One transfer ≈ 60 source requests
Based on a typical 2,000-song library: paged reads of playlists, albums, likes and track metadata.
Switch adds ~120 more
On the destination side we spend one request to match each song and one to add it — those only appear on Switch.
Buckets reset monthly
Volume accumulates within a calendar month, and rates step down automatically as buckets fill.
Transfers per month24,000 transfers
1K10K100K1M
60 requests each · source only
Source reads
24,000 transfers × 60 requests
1.44M
Billable requests
source only — you own the destination
1.44M
First 5M @ €0.60
1.44M requests
€864
Estimated monthly bill
0.600 effective per 1,000
€864
04 · The fine print, in plain words

Questions procurement always asks.

What exactly is one request?

One HTTP call from us to a music streaming service — reading a page of playlists, fetching a track, creating a playlist entry. Calls to our own API are never metered.

Does a failed match cost anything?

The read that found no match counts, because we made it. A provider error we retry does not — those retries are on us.

How does the minimum work?

We bill the greater of your metered usage and €500. There's no rollover: an unused month doesn't credit the next one.

Can we mix Core and Switch?

Yes. Many customers ship Switch to get live, then move high-volume flows onto Core. Both feed one meter and one invoice.

Are there overage penalties?

None. Rates only ever go down as you cross buckets, and there's no cap on volume in bucket 3.

What about annual commitments?

Above 25M requests a month we'll price a committed-volume contract with a custom floor rate. Talk to sales.

Start on sandbox. Pay when you go live.

Sandbox requests aren't metered and the €500 minimum starts on your first production call. Annual commitments and custom floors are available above 25M requests a month.

Prices in EUR, excl. VAT. Invoiced monthly.