Agrovision · OAuth Scopes
Agrovision OAuth Scopes
OAuth 2.0
probed
Agrovision 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.
CompanyAgricultureFood and BeverageConsumer Packaged GoodsAgriculture TechnologyE-CommerceRetailSupply ChainAgentic CommerceUniversal Commerce Protocol
Scopes: 0
Flows:
Method: probed
Scopes (0)
Agrovision 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.
The anonymous UCP MCP endpoint at /api/ucp/mcp requires none of these scopes for catalog, cart or checkout construction; they gate shopper-identity-bound operations only.
The anonymous UCP MCP endpoint at /api/ucp/mcp requires none of these scopes for catalog, cart or checkout construction; they gate shopper-identity-bound operations only.
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.