Benchmark Minerals · OAuth Scopes
Benchmark Minerals OAuth Scopes
OAuth 2.0
probed
Benchmark Minerals 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.
BatteriesCobaltCritical MineralsElectric VehiclesEnergy TransitionGraphiteLithiumLithium-IonMarket IntelligenceMiningNickelPrice ReportingRare EarthsSupply Chain
Scopes: 0
Flows:
Method: probed
Scopes (0)
Benchmark Minerals 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.
Benchmark runs two distinct permission vocabularies and publishes neither in prose. (1) The MCP gateway uses real OAuth 2.0 scopes, discoverable anonymously in its RFC 9728 protected-resource document. (2) The REST OpenAPI declares scope STRINGS on an apiKey security scheme — syntactically legal but semantically unusual, since an API key carries no scope grant; they read as an entitlement map describing which market a key must be subscribed to. Both sets are recorded verbatim; neither is invented.
Benchmark runs two distinct permission vocabularies and publishes neither in prose. (1) The MCP gateway uses real OAuth 2.0 scopes, discoverable anonymously in its RFC 9728 protected-resource document. (2) The REST OpenAPI declares scope STRINGS on an apiKey security scheme — syntactically legal but semantically unusual, since an API key carries no scope grant; they read as an entitlement map describing which market a key must be subscribed to. Both sets are recorded verbatim; neither is invented.
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.