Choose Login, Pay and AI scopes
Login, product payments and inference surcharges require separate capabilities and customer authorization.
| Use case | Scope | Allows |
|---|---|---|
| Log in with ShareAI | openid | A client-scoped account identity. Add profile or email only when needed. |
| Pay with ShareAI | payments | Create and inspect checkout requests for the connected account. The account owner or administrator confirms each debit. |
| AI surcharge | surcharge | Inference with the immutable AI billing terms accepted by the connected account. |
An identity-only token cannot call payment or surcharged inference endpoints. The requested scope must be enabled for the application and included in the authorization the customer accepted. Refreshing a token cannot add scopes.
A hybrid subscription uses payments for its periodic charge and surcharge for its AI usage. It needs both scopes. If its periodic price is positive, surcharged inference requires a paid, unexpired subscription period with the accepted price and interval.
An API key is a different authentication method; do not substitute it for a customer OAuth token. See payment requests and PKCE authorization.
Last updated September 18, 2026