Accounts payable on Arc · Settled in USDC
An agent that pays only what clears.
Cleared reads an invoice, checks it, and pays the vendor in USDC. The spending rules live in a treasury contract the agent cannot change, so even a fooled agent cannot overpay.
How a payment is decided
Three layers, each assuming the one before can fail.
- 01
The agent proposes
It reads the invoice and proposes a payment. It can misread, and it can be fooled by what it reads.
- 02
The policy engine decides
Code checks for duplicates, screening matches and limits, and records the reason for every decision, paid or refused.
- 03
The contract disposes
A treasury contract on Arc enforces the limits onchain. A compromised agent that skips every check still cannot exceed them.
The treasury contract
Limits the agent cannot change.
- Only the agent key can submit a payment.
- A vendor must be approved by the owner, with its own limit per payment.
- A daily cap limits total spending across all vendors.
- Each invoice can be paid once.
- Only the owner can approve vendors, change limits, replace the agent, or pause everything.
Scope
What this is, and is not.
Cleared is a testnet demo. Invoices enter through a form and are not yet read by a model. The screening list is sample data, not legal compliance. The contract has not been audited.
Console
Submit an invoice.
The agent checks it, then pays or refuses. Bypass simulates a compromised agent that skips every check, so the contract decides alone.
Try the same invoice twice, the unregistered vendor, an amount over the limit, or Northgate.
No entries yet.