Chance

A check you can look into.

See what was asked, what Chance found, and the record behind it.

The proposed action.

Your agent shares its instructions and what it wants to do.

A closer look.

Chance compares the action with those instructions and returns its decision.

A record you can inspect.

Open a completed check to see its result and the evidence available for it.

Open your checks ↗
Technical architecture and proof details
Under the hood

What it looks like inside

Chance is the verification harness between an agent's intent and its execution. Five parts work together so that every verdict it produces is recorded as it happens, signed inside sealed hardware, and written to a public blockchain. Anyone can then re-check the whole thing from their own browser, trusting no one in the middle.

run a decisionreason + researchsign · key sealed insideanchor the recordverify: read-only, in your browserYour browserconsole + independent verifierChance Harnesscloud service · orchestratorAI modelreasoning + live web searchConfidential enclaveTEE · sealed signing keyPublic blockchainBase · permanent record

How a decision flows

1Run

The agent reasons and searches the web; every step is sealed into a tamper-proof record as it happens.

2Sign

A key inside the confidential enclave signs the result, proving which exact program produced it.

3Anchor

The signed result is written to a public blockchain: permanent, timestamped, unchangeable.

4Verify

Your browser re-derives everything and checks it against the chain. Trust no one; recompute it.

What no one can fake

Guaranteed
  • ✓Every result is tamper-evident: alter one byte and it shows.
  • ✓It's attributable to the exact code that produced it (sealed in hardware).
  • ✓Once anchored, it's permanent and can't be quietly changed or denied.
  • ✓Anyone can re-verify it independently, with no trust in Chance required.
Who can do what
  • ·The operatorcan run agents, but can't sign as the judge or edit a published record undetectably.
  • ·The cloud hostruns the program, but can't read the sealed key out of the enclave.
  • ·Anyone with a linkcan read and re-verify a result, but can't forge or change one.
This is live, not a mock-up
  • ·The decision registry is a smart contract deployed on Base mainnet: every anchored decision is a real, public transaction.
  • ·The signing key runs in a genuine AMD SEV-SNP confidential enclave on Microsoft Azure, attested in hardware on every run.
  • ·The agent runs on a current frontier model with live web search.
See it for yourself

Create an account and run your first verification. Every verdict comes with a hash-chained, judge-signed receipt anchored on Base.

Get started