Space Frontiers · OAuth Scopes
Space Frontiers OAuth Scopes
OAuth 2.0
searched
Space Frontiers 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.
ResearchScholarly SearchFull-Text SearchRetrievalRAGPatentsDocumentsOCRDocument RecognitionMCPA2AAgent-NativeAI AgentsDataSearch
Scopes: 0
Flows:
Method: searched
Scopes (0)
Space Frontiers 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 OpenAPI declares no oauth2 securityScheme (derive-oauth-scopes.py correctly found nothing); OAuth 2.1 access tokens are accepted by the REST API through the bearer_auth http scheme ("Send the same API key, or an OAuth 2.0 access token, as a Bearer token") and by the MCP server. The scope vocabulary therefore comes from the RFC 8414 / RFC 9728 metadata and auth.md, all provider-published and fetched live on 2026-09-19.
The OpenAPI declares no oauth2 securityScheme (derive-oauth-scopes.py correctly found nothing); OAuth 2.1 access tokens are accepted by the REST API through the bearer_auth http scheme ("Send the same API key, or an OAuth 2.0 access token, as a Bearer token") and by the MCP server. The scope vocabulary therefore comes from the RFC 8414 / RFC 9728 metadata and auth.md, all provider-published and fetched live on 2026-09-19.
📄 Provider scope reference: https://api.machinelibrary.ai/auth.md
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.