M.Gemi · OAuth Scopes
M.Gemi OAuth Scopes
OAuth 2.0
probed
M.Gemi 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.
CompanyRetailE-CommerceFashionFootwearDirect to ConsumerAgentic CommerceUniversal Commerce ProtocolMCPShopifyCatalogCheckout
Scopes: 0
Flows:
Method: probed
Scopes (0)
M.Gemi 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 are advertised by the Shopify Customer Account OIDC/RFC 8414 discovery documents served on M.Gemi's own store host for M.Gemi's shop tenant. M.Gemi publishes no scope reference page of its own; these are the values the server itself declares in scopes_supported.
Scopes are advertised by the Shopify Customer Account OIDC/RFC 8414 discovery documents served on M.Gemi's own store host for M.Gemi's shop tenant. M.Gemi publishes no scope reference page of its own; these are the values the server itself declares in scopes_supported.
📄 Provider scope reference: https://mgemi.com/.well-known/oauth-authorization-server
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.