Coinme OAuth Scopes
Coinme publishes 3 OAuth 2.0 scopes via the authorization_code, refresh_token, client_credentials, and device_code flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Coinme 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.
Scopes (3)
| Scope | Description | Flows |
|---|---|---|
| openid | OIDC authentication; issue an ID token for the authenticated Coinme user. | |
| profile | Access the user's basic profile claims. | |
| Access the user's email address. |
📄 Provider scope reference: https://auth.coinme.com/.well-known/openid-configuration
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.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for oauth scopes
4 MCP tools reach this
find_scopesBrowse and filter every scope set in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/scopes/coinme-scopes"
curl "https://apis.io/api/v1/scopes?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.