Flutterwave Agentic Access
Flutterwave exposes 57 API operations that an AI agent could call, of which 27 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: 30 read, 8 write, and 19 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 | /chargebacks | physical | conditional |
| PUT | /chargebacks/{id} | physical | conditional |
| POST | /charges | physical | conditional |
| PUT | /charges/{id} | physical | conditional |
| POST | /direct-transfers | physical | conditional |
| POST | /orchestration/direct-charges | physical | conditional |
| POST | /orchestration/direct-orders | physical | conditional |
| POST | /orders | physical | conditional |
| PUT | /orders/{id} | physical | conditional |
| POST | /payment-methods | physical | conditional |
| POST | /refunds | physical | conditional |
| POST | /transfers | physical | conditional |
| POST | /transfers/rates | physical | conditional |
| POST | /transfers/recipients | physical | conditional |
| DELETE | /transfers/recipients/{id} | physical | conditional |
| POST | /transfers/senders | physical | conditional |
| DELETE | /transfers/senders/{id} | physical | conditional |
| PUT | /transfers/{id} | physical | conditional |
| POST | /transfers/{id}/retry | physical | conditional |