Cloverly Agentic Access
Cloverly exposes 22 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: 7 read, 6 write, and 9 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 | /2019-03-beta/estimates/shipping | physical | conditional |
| POST | /2019-03-beta/purchases | physical | conditional |
| POST | /2019-03-beta/purchases/carbon | physical | conditional |
| POST | /2019-03-beta/purchases/currency | physical | conditional |
| POST | /2019-03-beta/purchases/electricity | physical | conditional |
| POST | /2019-03-beta/purchases/flights | physical | conditional |
| POST | /2019-03-beta/purchases/shipping | physical | conditional |
| POST | /2019-03-beta/purchases/vehicle | physical | conditional |
| DELETE | /2019-03-beta/purchases/{slug} | physical | conditional |