Chord · OAuth Scopes
Chord OAuth Scopes
OAuth 2.0
probed
Chord publishes 5 OAuth 2.0 scopes. Scopes are the fine-grained permissions an application requests at authorization time to act against the Chord API on a user’s behalf.
This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.
CommerceComposable CommerceHeadless CommerceOrder ManagementOMSCustomer Data PlatformCDPEvent TrackingCommerce AnalyticsCustomer Lifetime ValueAI AgentsCommerce CopilotSolidusSpreeRuby on RailsShopifyDirect to Consumer
Scopes: 5
Flows:
Method: probed
Scopes (5)
| Scope | Description | Flows |
|---|---|---|
| openid | OIDC — issue an ID token for the authenticated Chord user. | |
| profile | OIDC — basic profile claims for the Chord user. | |
| OIDC — the Chord user's email address. | ||
| offline_access | Issue a refresh token so the MCP client can reconnect without re-consent. | |
| phone | OIDC — phone claim. |
📄 Provider scope reference: https://docs.chord.co/chord-mcp
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.