Clover Agentic Access
Clover exposes 36 API operations that an AI agent could call, of which 18 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: 18 read, 9 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 | /invoicingcheckoutservice/v1/checkouts | physical | conditional |
| POST | /v1/charges | physical | conditional |
| POST | /v1/charges/{chargeId}/capture | physical | conditional |
| POST | /v1/refunds | physical | conditional |
| POST | /v3/merchants/{mId}/orders | physical | conditional |
| POST | /v3/merchants/{mId}/orders/{orderId} | physical | conditional |
| DELETE | /v3/merchants/{mId}/orders/{orderId} | physical | conditional |
| POST | /v3/merchants/{mId}/orders/{orderId}/line_items | physical | conditional |
| POST | /v3/merchants/{mId}/orders/{orderId}/payments | physical | conditional |