OpenChainGraph Suite · CONTRACT A3 · arch #5

x402 V2 Batch-Settlement Reconciliation

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-A. Voucher-to-onchain batch reconciliation + settlement-risk window (ART-61) -> independent Merkle re-verification (cry-04) -> one Merkle-root settlement receipt (cry-05). The flagship Wave-14 runtime decision: did this batch of agent micro-payments settle correctly?

OpenChainGraph · 3 Steps cryptographic mandate Hash-Anchored §4 chain_depth:3 Client-Side · Zero PII
Chain Topology — x402 V2 Batch-Settlement Reconciler → Merkle Batch Verifier → Agent-Action Audit-Trail Aggregator
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 3 Steps
1 ROOT · D0 node
x402 V2 Batch-Settlement Reconciler art-61-x402-batch-settlement-reconciler
recon_verdict and merkle_root (H1) feed the batch verifier
MCP Call · reconcile_x402_batch_settlement
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "reconcile_x402_batch_settlement",
    "arguments": {}
  },
  "id": 1
}
↓
2 D2 node
Merkle Batch Verifier cry-04-merkle-batch-verifier
verified integrity (H2) feeds the aggregator
MCP Call · verify_merkle_batch
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "verify_merkle_batch",
    "arguments": {}
  },
  "id": 1
}
↓
3 TERMINAL · D3 node
Agent-Action Audit-Trail Aggregator cry-05-agent-action-audit-trail-aggregator
Exports composite batch-settlement artifact with execution_hash (H3), final stage
MCP Call · aggregate_execution_receipts
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "aggregate_execution_receipts",
    "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: After the x402 batch closes, how many settled receipts does the evidence pack actually hold?
Run the AINumbers MCP tool `run_chain` with {"chain":"agent-economy-batch-settlement"} and read `cry-05-agent-action-audit-trail-aggregator.n_receipts`.
Re-run with `inputs` for `cry-05-agent-action-audit-trail-aggregator`, reusing the values that result echoed, with `artifacts` changed so one settled voucher receipt joins the batch. 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/agent-economy-batch-settlement.html