How it works
Register your app — the per-app SSO fee is the publishing gate — and drop “Login with Muso” into your sign-in — standard OpenID Connect, the same flow you already use for Google or Apple.
Your user signs in with their own Muso account and approves what your app may see. Nothing happens without their consent, and they can revoke it anytime.
Your app receives a token scoped to that user. Call the API with it and render exactly what their membership entitles — pulled live at the moment they view it.
What your user sees
The token you receive is scoped to the signed-in user’s own entitlement — never more than their membership grants.
Every recording and role tied to the signed-in user’s Muso profile.
Their credits plus the analytics their Pro membership includes — chart positions, scores, and popularity for their own profile.
A flat capability fee — never a per-call meter. Add it to as many apps as you publish; each registered app is one line on one invoice.
Login with Muso isn’t the catalog API — your users are viewing their own account data, live and with consent, so the no-storage and no-redistribution terms that govern the catalog API don’t apply here. See how the two models differ →