Ironfang · OAuth Scopes
Ironfang OAuth Scopes
OAuth 2.0
searched
Ironfang 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.
Developer ToolsScreenshot APIWebsite ScreenshotHTML-to-PDFPDF APIImage APIOG Image APIQR Code APIWebsite-to-VideoRendering InfrastructureMCPUK-hosted
Scopes: 0
Flows:
Method: searched
Scopes (0)
Ironfang 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 - the published contract declares only the apiKey bearer scheme, so nothing was derivable. Every scope below was read from Ironfang's own published scope tables. Two scope systems share one vocabulary: API-key scopes chosen at key creation (REST), and OAuth scopes granted at MCP consent.
derive-oauth-scopes.py found no oauth2 securityScheme in the OpenAPI - the published contract declares only the apiKey bearer scheme, so nothing was derivable. Every scope below was read from Ironfang's own published scope tables. Two scope systems share one vocabulary: API-key scopes chosen at key creation (REST), and OAuth scopes granted at MCP consent.
📄 Provider scope reference: https://ironfang.uk/docs/mcphttps://ironfang.uk/renderwolf/docs#scopes
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.