Paigo · OAuth Scopes
Paigo OAuth Scopes
OAuth 2.0
derived
Paigo 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://auth.paigo.tech/oauth/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.
BillingUsage-Based BillingMeteringInvoicingPricingSoftware-as-a-ServiceSubscriptionDeveloper ToolsFinOps
Scopes: 0
Flows: clientCredentials
Method: derived
OAuth endpoints
Token URL
https://auth.paigo.tech/oauth/token
https://auth.paigo.tech/oauth/token
Flows
clientCredentials
clientCredentials
Scopes (0)
Paigo 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.
Paigo uses an OAuth 2.0 client_credentials flow (token from https://auth.paigo.tech/oauth/token with client ID/secret from Settings > API) and does not document or use OAuth scopes (https://docs.paigo.tech/overview/getting-started-with-paigo).
Paigo uses an OAuth 2.0 client_credentials flow (token from https://auth.paigo.tech/oauth/token with client ID/secret from Settings > API) and does not document or use OAuth scopes (https://docs.paigo.tech/overview/getting-started-with-paigo).
📄 Provider scope reference: https://docs.paigo.tech/overview/getting-started-with-paigo
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.