Gemini Trust Company · OAuth Scopes
Gemini Trust Company OAuth Scopes
OAuth 2.0
probed
Gemini Trust Company 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.
CompanyCryptocurrencyExchangeTradingMarket DataOrder ManagementClearingCustodyFinancial ServicesPrediction MarketsStakingDerivativesWebSocketFIXReal-TimeA2A
Scopes: 0
Flows:
Method: probed
Scopes (0)
Gemini Trust Company 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.
These scopes are NOT in either OpenAPI - neither spec declares an oauth2 securityScheme, so the derive-from-spec path returns nothing. They come from the provider's live RFC 8414 authorization-server metadata, which is the authoritative machine-readable source. 33 scopes, resource:action shaped.
These scopes are NOT in either OpenAPI - neither spec declares an oauth2 securityScheme, so the derive-from-spec path returns nothing. They come from the provider's live RFC 8414 authorization-server metadata, which is the authoritative machine-readable source. 33 scopes, resource:action shaped.
📄 Provider scope reference: https://developer.gemini.com/authentication/oauth
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.