BudgetPixel · OAuth Scopes
BudgetPixel OAuth Scopes
OAuth 2.0
probed
BudgetPixel 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.
Generative AIAI Image GenerationAI Video GenerationAI Music GenerationAudio GenerationContent ModerationCreative ToolsDesignagent-nativeMCPMCP ServerArtificial IntelligenceImage ModelsVideo ModelsMusic/Audio GenerationGenerative Mediallms-txtMedia ProcessingText-to-ImageText-to-VideoUpscalingCreditsModel AggregatorAgent Card
Scopes: 0
Flows:
Method: probed
Scopes (0)
BudgetPixel 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.
derive-oauth-scopes.py found no oauth2 securityScheme in the OpenAPI -- correctly, because the REST API is bearer-API-key only and has no scope surface at all. The OAuth surface belongs entirely to the MCP server, and these scopes were read from its live RFC 8414 metadata document rather than from a spec.
derive-oauth-scopes.py found no oauth2 securityScheme in the OpenAPI -- correctly, because the REST API is bearer-API-key only and has no scope surface at all. The OAuth surface belongs entirely to the MCP server, and these scopes were read from its live RFC 8414 metadata document rather than from a spec.
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.