Motomarks · OAuth Scopes
Motomarks OAuth Scopes
OAuth 2.0
probed
Motomarks 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.
AutomotiveLogoImage CDNManufacturerBrand AssetsImageCDNDeveloper ToolsAgent-NativeMCPReference Data
Scopes: 0
Flows:
Method: probed
Scopes (0)
Motomarks 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.
Scopes read from the live RFC 8414 authorization-server metadata (HTTP 200, 2026-09-09), which backs the MCP OAuth 2.1 flow. These are identity-shaped scopes only; API capability is governed by the account's plan and key type rather than granular OAuth scopes, and the docs publish no additional scope reference.
Scopes read from the live RFC 8414 authorization-server metadata (HTTP 200, 2026-09-09), which backs the MCP OAuth 2.1 flow. These are identity-shaped scopes only; API capability is governed by the account's plan and key type rather than granular OAuth scopes, and the docs publish no additional scope reference.
📄 Provider scope reference: https://motomarks.io/docs/mcp
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.