Get started
Whire documentation
Whire lets software pay people and businesses under rules a human signed. A payer signs a mandate — who may be paid, how much per payment, how much in total, until when — and every payment is checked against it before money moves. The answer is a signed receipt anyone can verify.
/mcp, for agents.x402 over SEPAAn agent pays for a web resource with a bank transfer.How it works#
- The payer signs up and is verified by a person.
- The payer signs a mandate for one payee, with a cap per payment and optionally in total.
- An agent asks whether a payment may proceed. Ten named checks run; the decision comes back as a signed receipt.
- A payout is created under the mandate, reviewed (KYC), and executed through a settlement rail.
An approval permits a payment; it does not reserve or move money. Settlement is a plug-in rail, and the sandbox runs a simulation that produces every outcome a bank can, including failures, on demand.
Choose how to connect#
| You are building | Start with |
|---|---|
| A backend in Python | Python SDK |
| An agent on OpenAI, Anthropic or similar | Agent toolkit |
| A desktop or coding agent (Claude, Cursor, Inspector) | MCP server |
| A backend in any other language | REST API |
| A seller that charges agents per request | x402 over SEPA |
The sandbox#
Everything here runs against https://sandbox.whire.ai. It uses simulated money, so nothing real ever moves, and its data is shared and reset on every deploy. Send your key as X-API-Key; GET /api/capabilities needs none and tells you what the deployment can do.
The MCP explorer lists every tool and lets you call it from a form.