Kushki Agentic Access
Kushki exposes 28 API operations that an AI agent could call, of which 20 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: 8 read, 7 write, and 13 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 | /card/v1/capture | physical | conditional |
| POST | /card/v1/charges | physical | conditional |
| POST | /card/v1/deferred | physical | conditional |
| POST | /cardpresent/v1/charges | physical | conditional |
| POST | /cardpresent/v1/charges/{ticketNumber}/void | physical | conditional |
| POST | /cash/v1/charges | physical | conditional |
| DELETE | /cash/v1/charges/{ticketNumber} | physical | conditional |
| POST | /payouts/transfer/v1/batch | physical | conditional |
| POST | /payouts/transfer/v1/init | physical | conditional |
| POST | /subscriptions/v1/card/{subscriptionId}/charge | physical | conditional |
| POST | /transfer/v1/charge | physical | conditional |
| POST | /transfer/v1/init | physical | conditional |
| DELETE | /v1/charges/{ticketNumber} | physical | conditional |