Teya Agentic Access
Teya exposes 42 API operations that an AI agent could call, of which 29 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: 13 read, 17 write, and 12 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 | /poslink/v1/tabs/{tab_id}/bill | physical | conditional |
| POST | /poslink/v1/tabs/{tab_id}/payment-intents | physical | conditional |
| PATCH | /poslink/v2/payment-requests/{payment-request-id} | physical | conditional |
| POST | /poslink/v2/refunds | physical | conditional |
| POST | /poslink/v3/payment-requests | physical | conditional |
| DELETE | /v1/tokens/{token_id} | physical | conditional |
| POST | /v1/transactions/moto | physical | conditional |
| POST | /v2/checkout/sessions | physical | conditional |
| POST | /v2/payment-links | physical | conditional |
| PATCH | /v2/payment-links/{payment_link_id} | physical | conditional |
| POST | /v3/refunds | physical | conditional |
| POST | /v3/refunds | physical | conditional |