Arcanum
Arcanum gives AI agents their own USDC wallets on Arc, with spending rules that are enforced by smart contracts. The agent can pay for what it is allowed to pay for. Anything outside the rules is refused, held for human approval, or freezes the wallet.
Arcanum never holds your funds. Each wallet is a contract that you own, and no Arcanum address can move money out of it.
How a payment works
- The agent asks to pay. It calls
executeUSDCon its wallet with a recipient, an amount and a reason. - The wallet checks the rules. The contract compares the payment with the wallet’s policy: per-payment, daily and monthly limits, the list of approved vendors, and spending categories.
- The contract decides. It returns one of four outcomes:
| Outcome | What happens |
|---|---|
| Allow | The USDC is sent in the same transaction. |
| Escalate | The payment is held until enough of the owner’s approvers sign. |
| Deny | The transaction reverts. No money moves. |
| Freeze | The wallet stops all payments until the owner reviews it. |
Every outcome happens on Arc, in the wallet contract itself. The dashboard and SDKs only read and submit transactions; they cannot override a decision.
Choose where to start
- Developers building agents: start with the Quickstart, then the TypeScript or Python SDK.
- Operators who approve payments: use the hosted app at thearcanum.in and read Escalations.
- Reviewers from Arc, Circle or a grant or hackathon panel: read How it works, the Security model and Admin and governance.
Current status
- Network: Arc Mainnet (chain 5042), live since 16 September 2026.
- Token: native Arc USDC.
- Source: contracts, SDKs and these docs are public on GitHub.
- Testing: Foundry unit, fuzz, invariant and attack tests. No external audit yet.
- SDKs: TypeScript on npm (
arcanum-sdk3.0.0); Python installed from source.
⚠️
The contracts have not had an external audit. Keep wallet limits small while the pilot runs.