SSO · OpenID Connect

Login with Muso.

Users sign in with their Muso account, so your app knows who they are. Sharing their own credits with your app (with consent, never metered) is shipping. Distinct from the paid catalog API.

How it works

1
Add the button

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.

2
The user consents

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.

3
Know who they are

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.

Sign-in
Live

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.

Their own credits
Shipping

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.

Simple pricing
$99/mo per registered app

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.

It’s the user’s own data

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 →

Ready to add it?

Subscribe to the per-app fee, we register your app, and you wire the OIDC flow.