Data use & termsLicensed for in-app consumption only.
Your subscription licenses Muso credits & stats for use INSIDE your own application, for your own users. It does not grant the right to resell, redistribute, or feed Muso data into another product or service — and it is a LIVE license: data is fetched from the API at the moment of use, never stored on your side.
The license, in plain terms
No resale
You may not sell, sublicense, or otherwise make Muso data available to third parties as data.
No redistribution
Data may not be re-exposed via your own bulk API, export, or feed in a way that reconstitutes the Muso graph.
No model/DB cloning
You may not use the API to systematically replicate the catalog or train a competing credits/stats database.
No caching or storage
Muso data must be requested live from the API at the time of use. API responses may not be cached, stored, retained, or written to any database, file, index, or datastore beyond the transient in-memory handling of the current request.
Storage is an Enterprise arrangement
Need to cache or store Muso data locally? Enterprise agreements include a term-limited storage license: you may cache and store licensed data locally for the duration of your agreement, under its security controls, with certified deletion when the agreement ends. Standard plans remain live-use only — talk to sales.
Express written consent
Any use beyond in-app consumption requires written consent from Muso. When in doubt, ask.
Rate limits, quotas, the spend ceiling, and per-record watermarks exist specifically to keep the database from being cloned. Money buys past your included quota — never a licence to take the catalog. Catalog-scale extraction is Enterprise-only under the data licence: a card on file does not buy it.
Two ways to use Muso — two sets of rules
The license terms above govern the Catalog API, where your app queries Muso data for your product. “Login with Muso” is a different thing entirely, and the no-storage / no-redistribution limits do not apply to it — a person is simply viewing their own data.
Catalog API
Paid · meteredYour application pulls Muso credits & stats to power your product. Live-use only — query at the moment of use, don’t cache, store, retain, resell, or redistribute. Storage & retention are an enterprise data agreement.
Login with Muso
User-consentedA person signs in with their own Muso account and sees, live, exactly the data their membership allows — credits on Lite, credits + analytics on Pro. It’s their own data, shown with their consent. The redistribution and storage limits that govern the Catalog API don’t apply to a user viewing their own account.
New to the SSO model? How Login with Muso works →
How we hold both sides to it
Live by design
Your app asks, the API answers, your user sees it — that's the whole data lifecycle. Nothing to sync, nothing to warehouse, nothing to age out.
Traceable responses
Every API response is traceable to the key that requested it. If licensed data shows up somewhere it shouldn't, we can tell exactly whose key it came from.
No bulk surface
There is no export file, database dump, or bulk feed — the API is the only way data leaves Muso, and it leaves one live request at a time.
Keys you control
Keys are scoped to your workspace, revocable from the console, and disabled automatically when a subscription ends.
Need to store, cache, or retain Muso data?
Standard plans never grant storage. Enterprise agreements explicitly do: a term-limited storage license lets you locally cache and store licensed data for the duration of the agreement, under its security controls, with certified deletion when the term ends — plus committed volume, support hours, custom rate limits, and catalog-scale access. Security questionnaires, DPAs, and compliance documentation are handled as part of the same agreement.
