Wyatt · OAuth Scopes
Wyatt OAuth Scopes
OAuth 2.0
probed
Wyatt 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.
CompanyBeautyPersonal CareHaircareConsumer ProductsE-CommerceRetailAgentic CommerceModel Context ProtocolSouth Korea
Scopes: 0
Flows:
Method: probed
Scopes (0)
Wyatt 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.
Read verbatim from scopes_supported in the two discovery documents Wyatt's domain serves. Two distinct scope vocabularies are published, and they do not overlap: the OIDC/authorization-server document advertises UCP-namespaced shopping scopes, while the RFC 9728 protected-resource document guarding the MCP endpoint advertises Cafe24's own mall.* scopes. Both are recorded as published; no scope was inferred.
Read verbatim from scopes_supported in the two discovery documents Wyatt's domain serves. Two distinct scope vocabularies are published, and they do not overlap: the OIDC/authorization-server document advertises UCP-namespaced shopping scopes, while the RFC 9728 protected-resource document guarding the MCP endpoint advertises Cafe24's own mall.* scopes. Both are recorded as published; no scope was inferred.
📄 Provider scope reference: https://developers.cafe24.com/app/front/app/develop/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.