Payments for AI agents, without giving them your keys
Agents are good at preparing payments and bad places to keep money. With send21 an agent creates payment requests and drafts through a scoped API key, and the payment is signed in a wallet the agent does not control.
Resources
Public and read-only, no key needed. They are built from the same sources as this site and the REST API, so they never disagree with them.
| URI | What it holds |
|---|---|
send21://docs/overview | What send21 is and is not, flows, currencies, fees and links (the same text as llms.txt) |
send21://docs/currencies | Every currency and network a payment can use, with the exact API values, and the 161 fiat currencies |
send21://fees/schedule | The fee schedule as JSON, the same as GET /api/v1/fees/schedule |
send21://docs/webhooks | Events, delivery headers, retries and the X-Send21-Signature-V2 check with code |
send21://brand/guidelines | Which logo for which background, colours, spacing, and the download URL of every logo file |
send21://brand/logo-horizontal-on-dark.svg | Main logo for dark backgrounds (also .png, 400 x 114) |
send21://brand/logo-stacked-on-dark.svg | Stacked logo for dark backgrounds and square spaces |
send21://brand/icon-on-dark.svg | The icon alone, for avatars and small spaces |
send21://brand/wordmark-on-light.svg | Wordmark for white or light backgrounds |
send21://brand/wordmark-on-dark.svg | Wordmark for dark backgrounds |
Prompts
Clients such as Claude offer these as ready-made commands. Each one steers the agent through the tools in an order that keeps the rules: your own addresses only, the payer signs in their own wallet, and a person decides about a payment with a different amount.
| Prompt | Arguments | What it does |
|---|---|---|
create_pay_link | amount, fiatCurrency, acceptedCurrencies, optional memo and orderId | Builds the options from your currencies and addresses, calls create_payment_request and returns the link |
check_payment | id (pay link or draft) | Reads the pay link or draft and explains in plain words where it stands |
handle_amount_mismatch | draftId | Shows what was billed and what arrived, and how you accept or decline it; it never decides for you |
Approved addresses: humans approve where the money lands
New accounts only let API keys use addresses the owner approved (receiving-address policy ApprovedOnly; older accounts can turn it on in Settings). A key that names any other address gets 422 address_not_approved and nothing is created, so a prompt-injected agent or a leaked key cannot point a payment at an address of its choosing.
The flow: the agent calls propose_receiving_address. The owner gets an email without any approve link, signs in to send21, compares the address character by character, and approves it with a passkey or an authenticator code. An emailed code is never enough, because an agent that reads the owner's inbox could use it. No API key and no scope can approve an address. get_account_status tells the agent what is still missing.
Pay links need the owner's own approved receiving addresses; drafts may pay any approved address. A pasted Lightning invoice names no address to approve, so with ApprovedOnly a key uses a Lightning address instead. Payments the owner creates in the app are not limited.
Agents sign up, owners take over
An agent without a key can call create_account (or POST /api/v1/accounts/agent-signup) with the owner's email address, its own name and what it will use the account for. It gets a bootstrap key at once (read, drafts and address-book scopes, valid 90 days, shown once), and the owner gets an email with a link to take the account over.
Until the owner opens the link (valid 72 hours) and sets up a passkey or a password, the key can read, propose addresses and call get_account_status, but creating anything returns 403 owner_not_confirmed. After that the approved-address rules apply: the agent creates pay links only to addresses the owner approved. An owner who did not ask for the account deletes it from the same page; an account nobody takes over is deleted after 7 days. At most 3 agent sign-ups per network per day; an email that already has an account gets 409 account_exists, and the agent asks the owner for a key instead.
Agent proposes, human signs
- The agent calls
create_payment_requestorcreate_draftover MCP, or the same REST endpoints. - The payer, or the operator, reviews and signs in their own wallet.
- The agent follows the result through
get_draft_statusor a webhook. - A leaked key can create instructions but cannot spend anything, because send21 holds nothing.
Built for automation
- Idempotency keys make retries safe.
- Batch creation of up to 25 drafts per call, and recurring templates.
- Machine-readable pay pages and responses, with your order id echoed in every webhook.
- Discovery files for agents: /llms.txt, /llms-full.txt and /openapi.json.
Selling to agents
A webshop can let an AI agent complete checkout: the backend creates a payment request per order, the agent picks a currency and pays from its operator's wallet, and the shop marks the order paid on draft.confirmed.
Related
Get paid to your own wallet
Create a free account and send your first pay link, or try a test payment first. No subscription.
This page is also available as Markdown: /ai-agent-payments.md. Questions: integration@send21.io.