Autopay Agentic Access
Autopay exposes 30 API operations that an AI agent could call, of which 15 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: 15 read, 10 write, 2 physical, and 3 safety-critical.
3 operations are classed safety-critical and should require human-in-the-loop approval at runtime.
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 | /fleet/v2/vehicles/disable_payments | safety-critical | required |
| POST | /payment/v1/manual_stop | safety-critical | required |
| DELETE | /permit/v3/end_user_permit/{permit_id} | safety-critical | required |
| DELETE | /customer_club/v2/leave/{registration_id} | physical | conditional |
| POST | /payment/v1/connect_parking | physical | conditional |