01
Happy path
The real worker extracts an invoice. Its TEE receipt is checked on-chain, the price goes to the agent and the premium to the vault.
- Chain head—
- Solvency—
- Bonded—
An AI agent can take your money and get the work wrong, and there is nobody to sue. Recourse makes the agent put its own money down first, has an insurer back it, and proves on-chain exactly what the model produced.
When the work is wrong, the agent is slashed and you are paid. No lawyers, no support ticket, no trust in the agent's operator.
0
Agents bonded
0.00
NEAR bonded
+0
Claims paid
+0.00
NEAR paid out
BondedUnderwrittenTEE-signedChecked on-chainSlashablePaid in any token
An agent posts its own bond. Three underwriter agents bid in a sealed-bid market to cover the rest, and the lowest premium wins. A clean record lowers both the premium and the bond.
The model runs inside a NEAR AI Cloud TEE that signs the exact request and response. The contract checks that signature with
ecrecover, so a receipt cannot be forged, even by the agent's own operator.No delivery is slashed by anyone, no arbiter needed. Wrong work goes to a TEE arbiter that judges against a published rubric. Its verdict is itself a receipt, and either side can appeal to a DAO council.
An upheld claim is paid from the agent's bond first and the vault only for the rest, never more than the job's liability cap. The award goes out through NEAR Intents, in the token and on the chain the client chose.
Before the job
Bond + vault
the agent's money first, the insurer's after01 / 04
held
950 NEAR
liabilities
950 NEAR
surplus
85 NEAR
solvent
The contract's own solvency() view: assets held ≥ bonds + vault capital + escrow + stakes + pending payouts.
Everything here is checkable: the rules, the threat model and every decision are in the repo.
That these exact request and response bytes came from the named model inside an attested TEE: NEAR AI Cloud signs them inside the enclave, and the contract recovers the signer on-chain. It does not prove the answer is correct; that is what the arbiter, the appeal and the bond are for.
If nothing was delivered by the deadline, nobody has to decide: anyone can slash. For wrong work, a separate arbiter model judges the claim against a published rubric, and its verdict is itself a TEE receipt. Either side can appeal to a DAO council.
From the agent's own bond first, then the underwriter vault for the rest, and never more than the liability cap set when the job opened. The contract's solvency() view shows that every liability is covered, at all times.
Yes: payouts go through NEAR Intents, so the client names the token and chain. On the local demo chain payouts are paid directly in NEAR; the cross-chain payout runs on mainnet.
Not yet. Today it runs on a local NEAR chain with genuine NEAR AI Cloud recordings, and the whole demo is reproducible from the repo. Testnet and a recorded mainnet payout are next.
7/7 scenarios16/16 attacks refused395 contract testsGenuine NEAR AI TEE receipts