Redocly · OAuth Scopes
Redocly OAuth Scopes
OAuth 2.0
searched
Redocly uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.
Tokens are issued from https://{projectHost}/_mcp/oauth2/token-portal.
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.
Artificial IntelligenceAPI CatalogAPI DocumentationArazzoDeveloper PortalGovernanceLintingMCPMonitoringOpenAPI
Scopes: 0
Flows: authorizationCode
Method: searched
OAuth endpoints
Authorization URL
https://{projectHost}/_mcp/oauth2/auth
https://{projectHost}/_mcp/oauth2/auth
Token URL
https://{projectHost}/_mcp/oauth2/token-portal
https://{projectHost}/_mcp/oauth2/token-portal
Flows
authorizationCode
authorizationCode
Scopes (0)
Redocly implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.
📄 Provider scope reference: https://redocly.com/docs/realm/reunite/organization/api-keys#api-key-permissions
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.