The owner grants a mandate
Categories, an approved-vendor list, per-payment and daily, weekly and monthly caps, a human-approval threshold and an expiry. Held by MandateRegistry. No admin key, no pause switch.
Give an agent the keys to a company's money and it needs a limit it cannot argue with, and a record you can replay. Credentia enforces both on-chain.
The film
Every figure, address and hash on screen comes from the live deployment. Captions are on.
How it works
The registry is a policy ledger, not custody: it holds no funds. It decides whether a payment is allowed, and the agent can only act inside that answer.
Categories, an approved-vendor list, per-payment and daily, weekly and monthly caps, a human-approval threshold and an expiry. Held by MandateRegistry. No admin key, no pause switch.
Each request is validated on-chain, the spend is recorded, then USDC is sent through Arc's USDC contract. Over the limit or an unknown payee is refused. At the threshold it waits for a signed human approval.
Paid, refused or escalated, each outcome is appended to DecisionLog with the transfer hash and the rule that failed. Records are hash-chained, so editing one breaks every later hash.
On-chain record
Everything below is on Arc testnet and opens in the public explorer.
The six records of the demo run, each hashed together with the one before it.
Honest status. This is an unaudited testnet prototype and the demo business was created by the builders; there are no outside customers yet. The registry records and authorises spending but cannot move funds, so a compromised agent key could still send USDC outside it. Do not use real funds.