Zubale Agentic Access
Zubale exposes 21 API operations that an AI agent could call, of which 19 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: 2 read, 8 write, and 11 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 | /external-notification-handler/api/v1/events | physical | conditional |
| POST | /integration/finalOrder | physical | conditional |
| POST | /it/api/v1/{brand_name}/pnp_delivery/jobs | physical | conditional |
| POST | /orders/api/pnp_delivery/jobs/sync | physical | conditional |
| POST | /orders/api/pnp_e2e/jobs | physical | conditional |
| PUT | /orders/api/{brandId}/cancel | physical | conditional |
| PUT | /orders/api/{brand_id}/cancel | physical | conditional |
| POST | /smart-hub/api/cencosud/coordinates | physical | conditional |
| POST | /smart-hub/api/cencosud/order | physical | conditional |
| PUT | /smart-hub/api/cencosud/orders/states | physical | conditional |
| POST | /webhook | physical | conditional |