RSL Collective · OAuth Scopes
RSL Collective OAuth Scopes
OAuth 2.0
none
RSL Collective 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.
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.
CompanyAI LicensingContent LicensingCollective RightsPublishersRoyaltiesNonprofitRSL Standard
Scopes: 0
Flows:
Method: none
Scopes (0)
RSL Collective 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.
OLP is documented as an OAuth 2.0 extension (client_credentials grant), but the /token request defines no `scope` parameter: the granted rights are expressed by the RSL XML element sent in the request (permits/prohibits usage such as search, ai-train, ai-input). The only scope-like term in the spec is the /key error `insufficient_scope` ("The license does not permit access to the encryption key for this resource."). No OAuth scope list is published.
OLP is documented as an OAuth 2.0 extension (client_credentials grant), but the /token request defines no `scope` parameter: the granted rights are expressed by the RSL
📄 Provider scope reference: https://rslstandard.org/rsl
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.