AINumbers.co · chain prompts

What happens when you paste a workflow prompt

Every chain page carries an Ask your agent paragraph. This walkthrough follows the one on the AP2 payment-receipt chain from the copy button to a verified answer. The dashed lines show which machine does each part.

Goal of this animation

Show what happens, machine by machine, after you paste a chain page's Ask your agent prompt into an AI assistant, from the first tool call to a verified hash.

🔒 No personal dataThe prompt asks for synthetic inputs, and the MCP worker processes each call once without storing or logging it. Every value shown is synthetic.
☁ Our server is Cloudflare“AINumbers server” means Cloudflare today. The MCP worker runs on Cloudflare Workers and the chain pages are delivered through Cloudflare's network.
What the colours mean on this page
● green · the check passed and the step may go ahead● amber · held, flagged for review or waiting on something● red · refused, or a mismatch was caught
MATCH · step 7verify_execution_hash recomputed the composite hash and got the same value, so the artifact is exactly what the worker produced.
CHANGED · run 2Amber marks a value that moved because the prompt asked it to. Adding one executed payment receipt to cry-05 changes that step's hash and the session root. Steps 1 and 2 keep their hashes, which shows nothing else moved.
NO REFUSALS HEREEvery step ran. A refusal would come back the same way, as a step with its own hash and a verdict saying why.
0.0s

Start the walkthrough

The prompt word for word

This is the paragraph on the chain page, generated from chaingraph/chain-prompts/agent-economy-payment-receipt.json. Paste it into Claude or any MCP-aware agent that has the AINumbers server connected.


       
    

Reading the result

steps[].inputs_source says where each step's inputs came from: fixture on the first run, caller for the step you changed.

parent_hashes threads each step's execution_hash into the next step, so the chain cannot be reordered or spliced.

composite_execution_hash covers every step that ran. verify_execution_hash recomputes it from the artifact, and identical inputs always give the identical hash.

The prompt text and the response field names are taken from the chain page and the MCP worker source. The chat replies are an illustrative transcript, the input values are fixture-style placeholders and the hashes are SHA-256 over demo strings computed in this page. In this door the kernels run on our Cloudflare Worker, which keeps no payloads. The other doors are on Three doors to the same workflows.

←→ back and next · Space play or pause · all explainers