Per-payment cap
The largest single payment the vault will release, whatever the agent asks for.
An agent that pays real invoices on Arc, from a vault it cannot withdraw from. The owner sets the limits on-chain, so even a leaked key can only spend what you allowed.
Open source · github.com/angelraph/arcurrent
Real numbers, read from Arc mainnet when you load the page.
On the open MandateEscrow contract
Released to payees, read from the chain
Source published on the explorer
The project never holds the vault owner key
The vault
The treasury sits in a contract, not in the agent's wallet. The owner sets four rules on-chain, and the vault refuses anything outside them.
The largest single payment the vault will release, whatever the agent asks for.
A rolling 24 hour budget that refills continuously, so there is no midnight reset to game.
The agent can only pay addresses the owner has approved. A new payee needs the owner's signature.
A separate key that can freeze the vault at once, and cannot move money or change any rule.
If the agent's key leaks
An agent on a normal wallet can lose everything in that wallet. An agent on an Arcurrent vault can lose at most the daily allowance, and only to payees you already approved.
Example: a $1000.00 treasury, the caps this vault runs on today.
That is 0.5% of the treasury, with the owner able to pause or replace the operator the moment it is noticed. The vault does not judge whether a payment is deserved; it bounds the damage.
Lifecycle
From the owner's first rule to the public record of a payment, each stage is enforced by the contract or readable by anyone.
Set the rules
Live activity
No mock-ups. On the left, the agent's own decision log. On the right, the escrow contract's own rows. Both are read live.
Obligation is denominated in EURC. StableFX access is gated (RFQ-based, pending Circle approval) and no conversion path is wired in yet, so this cannot be settled automatically. Paid the rate oracle 0.001 USDC via x402 for the current rate: 1 EUR = 1.1165 USD (as of 2026-11-06, api.frankfurter.dev).
Who it is for
For treasury owners
Fund a vault, set the caps, approve the payees. The agent handles the routine payments and you keep the pause switch.
Open the dashboard →For agent builders
An MCP server and a typed SDK let any agent pay through the vault. The vault, not the prompt, is the guardrail.
See the npm packages ↗For anyone getting paid
Enter an address and an amount, share the link, and the payer funds a mandate that releases when you deliver.
Create a payment request →Go deeper
Mechanism
The four-step loop, why it runs on Arc, what a compromised agent can and cannot do, and the stack underneath.
OpenDirection
What is shipped, what is next, and what has to happen before it holds real volume.
OpenAnswers
Plain answers to the questions people actually ask about custody, risk and audits.
OpenLive
Real balances, real obligations, real agent decisions, read straight from Arc mainnet.
OpenRead the live vault, check the contracts yourself, or fund a mandate with your own USDC. Nothing here asks you to take it on trust.