OpenChainGraph Suite · CONTRACT A3 · arch #5

Tempo Agentic Checkout

Note (dated 2026-08-04): a chain composes independent computations performed in an analytical order. No step's output is carried into the next step by the execution model; each step computes from its own declared inputs. This is true of every chain on this site, including chains whose per-step copy below reads as a data handoff.

W-D chain. x402/MPP protocol decode → TIP-20 settlement mapper.

OpenChainGraph · 2 Steps settlement mandate Hash-Anchored §4 chain_depth:2 Client-Side · Zero PII

Chain Topology — x402 Header Decoder, Payload Linter & 402 Flow Simulator → Tempo Agentic Checkout Settlement Mapper

§4 Execution Hash · Chain Definition Anchor

execution_hash:computing…

Chain Stages · 2 Steps

1 ROOT · D0 node

x402 Header Decoder, Payload Linter & 402 Flow Simulator art-26-x402-payload-decoder-flow-simulator

protocol_decode and payment_details feed Stage 2 TIP-20 settlement mapping

MCP Call · simulate_x402_flow

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "simulate_x402_flow",
    "arguments": {}
  },
  "id": 1
}

↓

2 TERMINAL · D2 node

Tempo Agentic Checkout Settlement Mapper art-40-tempo-agentic-checkout

Exports TIP-20 settlement artifact with execution_hash; memo → remittance_information crosswalk, final stage

MCP Call · map_tempo_settlement

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "map_tempo_settlement",
    "arguments": {}
  },
  "id": 1
}

Export Artifacts

Download the §4 chain definition artifact (hash-anchored composite JSON) or the §13.11 W3C Verifiable Credentials view. Both derive from the chain definition — no new hash is minted. Available after hash computation.

Ask your agent

Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this whole workflow on the server and check one field that answers a real question.

Question: A partner sent this x402 header for an agentic checkout. Will the decoder take it as well formed?
Run the AINumbers MCP tool `run_chain` with {"chain":"tempo-agentic-checkout"} and read `art-26-x402-payload-decoder-flow-simulator.is_json`.
Re-run with `inputs` for `art-26-x402-payload-decoder-flow-simulator`, reusing the values that result echoed, with `header_or_payload` set to "vouch exact {broken". Compare the same field.
Verify: call `verify_execution_hash` (https://mcp.ainumbers.co/mcp) with `claimed_hash` set to `composite_execution_hash` and the full `composite_artifact`.
Ledger, for a human re-check: https://ledger.ainumbers.co/
PII rule: send synthetic or anonymised inputs only. The MCP server runs these kernels and logs no payloads.
Chain page: https://ainumbers.co/chaingraph/chains/tempo-agentic-checkout.html