ClickSend Agentic Access
ClickSend exposes 42 API operations that an AI agent could call, of which 22 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: 20 read, 10 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 | /email/price | physical | conditional |
| POST | /email/send | physical | conditional |
| POST | /mms/price | physical | conditional |
| POST | /mms/send | physical | conditional |
| POST | /post/letters/price | physical | conditional |
| POST | /post/letters/send | physical | conditional |
| POST | /post/postcards/price | physical | conditional |
| POST | /post/postcards/send | physical | conditional |
| POST | /sms/price | physical | conditional |
| POST | /sms/send | physical | conditional |
| POST | /voice/price | physical | conditional |
| POST | /voice/send | physical | conditional |