Loopay Agentic Access
Loopay exposes 31 API operations that an AI agent could call, of which 9 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: 22 read, 2 write, and 7 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 | /payout/create | physical | conditional |
| POST | /payouts/byExternalIdentifierList | physical | conditional |
| POST | /payouts/create | physical | conditional |
| POST | /payouts/sign | physical | conditional |
| POST | /source-of-payment/create | physical | conditional |
| POST | /source-of-payment/create-direct-payment | physical | conditional |
| POST | /source-of-payment/update | physical | conditional |