UrbanPiper Agentic Access
UrbanPiper exposes 16 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: 2 read, 9 write, and 5 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 | /ext/api/v1/generic/pos/rider-location/ | physical | conditional |
| POST | /ext/api/v1/generic/pos/rider-status/ | physical | conditional |
| PUT | /external/api/v1/orders/{id}/status/ | physical | conditional |
| POST | /external/api/v1/webhooks/retry/ | physical | conditional |
| POST | /hub/api/v1/orders/items-oos/ | physical | conditional |