An open settlement primitive, and the autonomous agent that's already using it.
Arcurrent's treasury agent watches what you owe, decides when it's safe to pay from real signals, and settles by creating and releasing a mandate on MandateEscrow, an open, permissionless contract any address can fund, fulfill, or read. No human clicks approve. Every settlement is real, on Arc mainnet, and independently verifiable on-chain.
Why does this need a blockchain?
A normal payments API needs a human, or a trusted middleman, to authorize every transfer. Arcurrent can't work that way. The whole point is that it decides and acts on its own, on a schedule, with no one watching. That only works if the money it moves lives somewhere it can prove it controls without a password handed to it each time, every decision leaves a permanent record so a wrong payment is provable rather than a "trust us" in a database, and settlement is fast and cheap enough that checking a balance every few minutes doesn't cost more than the payments themselves. Arc is built for exactly this. Gas is paid in USDC, the same money moving through the system, rather than a separate token you have to keep topped up, and settlement finishes in under a second.
What's actually running under the hood
Developer-Controlled Wallets
The treasury wallet is a real Circle-custodied wallet, Live environment, the agent signs from directly. No private key lives in this codebase.
App Kit / Bridge Kit (CCTP)
When the balance runs low, the agent can bridge USDC in from a second wallet on another chain via Circle's Cross-Chain Transfer Protocol. Proven working on testnet; disabled on mainnet for now, pending a funded Live-environment source wallet.
x402 nanopayments
Before acting on a foreign-currency bill, the agent pays a sub-cent fee to a rate oracle for the live exchange rate. It's a real, working micropayment, not a placeholder.
MandateEscrow, an open primitive
Every payment is created and released as its own mandate on a permissionless contract: fund it, prove fulfillment, release atomically, with a reputation ledger that updates on-chain. Not project-owned · any address can fund, fulfill, or read it, and this agent is just its first live caller.
What to do next
- 1Open the dashboard and add an obligation: a vendor, an amount, a due date, USDC or EURC.
- 2Watch the decision log. The agent evaluates it against the real treasury balance and reserve floor, then pays it, waits, or flags a liquidity shortfall if the balance would run short.
- 3Click any transaction hash to verify it yourself on Arc's mainnet explorer, or check the Mandates table directly · it's a live read of on-chain state, not this project's own bookkeeping. Nothing here is simulated.