Metadata · OAuth Scopes
Metadata OAuth Scopes
OAuth 2.0
searched
Metadata 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.
CompanyMarketingMarketing AutomationDemand GenerationAdvertisingB2BArtificial IntelligenceMCPAI AgentsPaid MediaAccount Based Marketing
Scopes: 0
Flows:
Method: searched
Scopes (0)
Metadata 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.
Two distinct scope vocabularies. The seven PRODUCT scopes below are attached to API keys at mint time and gate MCP tool access. The OAuth authorization server separately advertises only the transport scopes openid and offline_access.
Two distinct scope vocabularies. The seven PRODUCT scopes below are attached to API keys at mint time and gate MCP tool access. The OAuth authorization server separately advertises only the transport scopes openid and offline_access.
📄 Provider scope reference: https://metadata.io/developers/authentication.html
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.