See how AINumbers works
Short animated pages you can pause and step through. They show where each calculation runs, which is usually on your own device, and how anyone can check the result afterwards. New here? Start with the first card.
2D walkthroughs
Each page has the same controls: play and pause, 0.5× to 2× speed, a timeline you can drag and a numbered step for each part of the story, with a short explanation underneath.
170 s · 9 stepsOne workflow step by step
An AI shopping agent wants to spend USD 120. Three small pages each answer one question on your device.
You will see pages, fingerprints, receipts and why it is called an inverted database.
269 s · 8 stepsChecking a calculation without redoing it
A bank says an outage is a major incident. A 256-byte seal lets you confirm the official rule gave that answer without seeing its data.
You will see what a proof covers, and the one thing it leaves to you.
367 s · 9 stepsHow MCP runs one workflow
An AI assistant checks whether a web bot is genuine using three AINumbers tools. Every message on the wire is shown in order.
You will see the handshake, the tool list, linked tool calls and where the math runs.
468 s · 9 stepsHow WebMCP runs one workflow
The same three checks run by an agent inside your browser. Each page registers its own tool and computes in its own tab.
You will see how a page offers a tool, and why no server sees the calls.
582 s · 9 stepsOne agent makes one purchase through three workflows
A single shopping agent is checked before, during and after a USD 120 payment. It goes stale and retries, and the double order is caught.
You will see who the agent is, both budgets, the held retry and one session receipt.
641 s · 16 stepsSeven workflows run on one inverted database
Twenty-one page runs, a Merkle root, public timestamps and an auditor. Switch the network off and watch the run finish anyway.
You will see what stays on your device, and the single hash that leaves it.
773 s · 9 stepsWhat happens when you paste a workflow prompt
The Ask your agent paragraph from a chain page, followed from the copy button through run_chain to a verified hash.
You will see how an AI host, our MCP worker and the public ledger split the work.
823 s · 7 stepsThree doors run the same workflows
WebMCP in your browser, the remote MCP server and Helm on your machine, with every step marked by where it computes.
You will see which door sends your inputs to our server and which never does.
952 s · 13 stepsHow a kernel becomes a 256-byte proof
Four real kernels through the RISC Zero pipeline: preflight, the GPU queue, segments, recursion, the Groth16 wrap and an offline check.
You will see cycle counts, the GPU singleton and what the seal binds.
10100 s · 12 stepsTen live runs sealed under one timestamp
A real agent session from 26 September 2026: x402 checks, a signed mandate, an escalation and EMIR pages, bound into one receipt that three authorities timestamped.
You will see real hashes, a refusal and an escalation on the record, and how to check the timestamps.
3D brick models
The same ideas built as stacks of bricks you can turn and take apart. Drag a scene to rotate it.
The AINumbers estate as a brick neighborhood
Each wall is one part of the estate and each road a documented link between parts. Seven journeys travel through it.
The Agent Staircase in 3D bricks
Every brick is one step from the Agent Staircase explainer and only snaps onto the bricks it depends on.
A ChainGraph workflow built brick by brick
Three tools run in order, each citing the hash before it, and the run folds into one timestamped composite.
Each explainer is a single page with its styles and scripts inside, and makes no network requests while it runs. Values are synthetic unless a page names its live source, and each page lists its sources at the bottom.