ChromaCode OAuth Scopes
ChromaCode publishes 12 OAuth 2.0 scopes via the authorizationCode and clientCredentials flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the ChromaCode API on a user’s behalf.
Tokens are issued from https://openid.chromacodecloud.com/auth/realms/apps/protocol/openid-connect/token.
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.
OAuth endpoints
https://openid.chromacodecloud.com/auth/realms/apps/protocol/openid-connect/auth https://openid.chromacodecloud.com/auth/realms/cloud/protocol/openid-connect/auth
https://openid.chromacodecloud.com/auth/realms/apps/protocol/openid-connect/token https://openid.chromacodecloud.com/auth/realms/cloud/protocol/openid-connect/token
authorizationCodeclientCredentials
Scopes (12)
| Scope | Description | Flows |
|---|---|---|
| chromacloud | ChromaCode Cloud application scope (provider-specific; no published definition). | |
| chromacloud:service_account | ChromaCode Cloud service-account scope for machine clients (provider-specific; no published definition). | |
| openid | Standard OIDC scope requesting an ID token. | |
| profile | Standard OIDC scope for basic profile claims (name, given_name, family_name, preferred_username). | |
| Standard OIDC scope for the email and email_verified claims. | ||
| address | Standard OIDC scope for the address claim. | |
| phone | Standard OIDC scope for phone_number and phone_number_verified claims. | |
| offline_access | Standard OIDC scope requesting a refresh token usable while the user is offline. | |
| roles | Keycloak client scope adding realm and client role mappings to the token. | |
| web-origins | Keycloak client scope adding allowed CORS web origins to the token. | |
| microprofile-jwt | Keycloak client scope emitting MicroProfile JWT claims (upn, groups). | |
| acr | Keycloak client scope carrying the authentication context class reference. |
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/chromacode-scopes"
curl "https://apis.io/api/v1/scopes?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.