Voyager Technologies · OAuth Scopes
Voyager Technologies OAuth Scopes
OAuth 2.0
searched
Voyager Technologies 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.
CompanySpaceDefenseAerospacePropulsionSatelliteLunarSpace StationsPublic Company
Scopes: 0
Flows:
Method: searched
Scopes (0)
Voyager Technologies 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.
Read verbatim from scopes_supported in the provider's RFC 8414 metadata and confirmed by the RFC 9728 protected-resource document (both HTTP 200, 2026-09-18). The single scope belongs to the WordPress MCP adapter's authorization server; there is no product API, no scopes reference page and no finer-grained permission model published.
Read verbatim from scopes_supported in the provider's RFC 8414 metadata and confirmed by the RFC 9728 protected-resource document (both HTTP 200, 2026-09-18). The single scope belongs to the WordPress MCP adapter's authorization server; there is no product API, no scopes reference page and no finer-grained permission model published.
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.