How it works
Subscribe to the per-app SSO fee and we register your app: client credentials and your redirect URIs. Then add “Login with Muso” to your sign-in. It is 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 on the consent screen. Nothing is shared without their consent.
Your app receives a signed id_token with a stable Muso user id. Reading the user's own credits with their token is shipping, not live yet.
What your app gets
Only the signed-in user’s own data, never the wider catalog.
Your users sign in with their Muso account (OpenID Connect), and your app learns who they are: a stable Muso user id, their name, email and photo.
Shipping, not live yet: with the member's consent (scope muso.credits.read), your app will read that member's own published credits with their access token. Never metered.
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 see their own account data, with their consent. Show what you get through Login with Muso only to the member who signed in. Public display to visitors who are not signed in, and any catalog-wide read, goes through your metered API key. See how the two models differ →
