Midtrans Agentic Access
Midtrans exposes 33 API operations that an AI agent could call, of which 21 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: 12 read, 7 write, 13 physical, and 1 safety-critical.
1 operation 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 | /v1/subscriptions/{subscription_id}/disable | safety-critical | required |
| POST | /iris/api/v1/payouts | physical | conditional |
| POST | /iris/api/v1/payouts/approve | physical | conditional |
| POST | /iris/api/v1/payouts/reject | physical | conditional |
| POST | /snap/v1/transactions | physical | conditional |
| POST | /v1/payment-links | physical | conditional |
| DELETE | /v1/payment-links/{order_id} | physical | conditional |
| POST | /v2/charge | physical | conditional |
| POST | /v2/{order_id}/approve | physical | conditional |
| POST | /v2/{order_id}/cancel | physical | conditional |
| POST | /v2/{order_id}/deny | physical | conditional |
| POST | /v2/{order_id}/expire | physical | conditional |
| POST | /v2/{order_id}/refund | physical | conditional |
| POST | /v2/{order_id}/refund/online/direct | physical | conditional |