Barogo Agentic Access
Barogo exposes 21 API operations that an AI agent could call, of which 14 are state-changing ‘acting’ operations. This is a recommended x-agentic-access execution contract — the scope, audience, consequence tier, short-lived token constraints, and escalation each action should carry before it is handed to an autonomous agent.
By consequence: 7 read, 2 write, and 12 physical.
Contracts are classified heuristically from the provider’s OpenAPI and refresh on every APIs.io network build; audience is bound per deployment. The model follows Curity’s Access Intelligence (apidays Munich 2026). Browse every provider’s agent contracts at agentic-access.apis.io.
By consequence
Highest-consequence actions
The physical and safety-critical operations an agent could invoke — the ones that most warrant scoped tokens, tight TTLs, and escalation. Full per-operation contracts are in the source below.
| Method | Path | Consequence | Human-in-loop |
|---|---|---|---|
| POST | /api/delivery-possible | physical | conditional |
| POST | /api/flexible/delivery-possible | physical | conditional |
| POST | /api/flexible/orders | physical | conditional |
| PUT | /api/flexible/orders/{orderAgencyOrderId}/delivery-price | physical | conditional |
| POST | /api/orders | physical | conditional |
| PUT | /api/orders/{orderAgencyOrderId}/drop-info | physical | conditional |
| PUT | /api/orders/{orderAgencyOrderId}/memo-info | physical | conditional |
| PUT | /api/orders/{orderAgencyOrderId}/payment-info | physical | conditional |
| PUT | /api/orders/{orderAgencyOrderId}/phone-info | physical | conditional |
| PUT | /api/orders/{orderAgencyOrderId}/pickup-wish-at | physical | conditional |
| POST | /api/orders/{orderAgencyOrderId}/prepare-complete | physical | conditional |
| PUT | /api/orders/{orderAgencyOrderId}/status/cancel | physical | conditional |