Alloy · OAuth Scopes
Alloy OAuth Scopes
OAuth 2.0
none
Alloy 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 /oauth/bearer.
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.
Identity DecisioningIdentity VerificationKYCKYBAMLFraud PreventionCredit UnderwritingOngoing MonitoringCase ManagementFintechBanking
Scopes: 0
Flows: clientCredentials
Method: none
OAuth endpoints
Token URL
/oauth/bearer
/oauth/bearer
Flows
clientCredentials
clientCredentials
Scopes (0)
Alloy 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.
The OAuth2 security scheme(s) in the OpenAPI declare no scopes, and no security requirement references one.
The OAuth2 security scheme(s) in the OpenAPI declare no scopes, and no security requirement references one.
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.