API reference
The Arcanum API serves the data the hosted app shows: wallets, payments, approvals and events indexed from Arc. It never signs or sends transactions. When the app helps you change something, the API prepares an unsigned transaction and you sign it in your wallet.
Agents do not need the API to pay; the SDKs talk to Arc directly.
Access
Every protected request uses a Sign-In with Ethereum (SIWE) session. Your organisation is taken from the session, never from the request, so a request cannot read another organisation’s data.
Areas
| Area | What it covers |
|---|---|
auth | Sign-in sessions. |
org | Your organisation and its members. |
wallets | Wallets, their policies and agents. |
agents | Agent details, payments and risk events. |
transfers | Payment history with filters. |
escalations | Held payments, and unsigned approve or reject transactions. |
vendors | Vendor lists, and unsigned vendor changes. |
policies | Unsigned policy changes and their transaction records. |
anomalies | Risk events and their review state. |
events | The raw event stream. |
analytics | Totals: value governed, active agents, payments blocked, pending approvals. |
receipts | Payment decision receipts. |
Receipt endpoints
Agent runtimes can use these REST endpoints directly:
| Method | Path | Purpose |
|---|---|---|
POST | /api/receipts | Request a receipt for a payment intent. |
POST | /api/receipts/{id}/evidence | Link a transaction to a receipt. |
POST | /api/receipts/verify | Verify a receipt. |
GET | /api/receipts/issuers | List the receipt issuer keys. |
See Receipts for what a receipt contains.