OpenChainGraph Suite · CONTRACT A3 · arch #5

Arc Agentic Commerce

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-E chain. Model agentic commerce economics on Arc — Paymaster gas abstraction + CPN settlement for autonomous agent payment flows.

OpenChainGraph · 3 Steps treasury mandate Hash-Anchored §4 chain_depth:3 Client-Side · Zero PII
Chain Topology — Arc Fit Diagnostic → Arc Paymaster Economics Model → Arc CPN Corridor Economics Model
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 3 Steps
1 ROOT · D0 node
Arc Fit Diagnostic art-42-arc-fit-diagnostic
arc_score → agentic commerce dimension primary
MCP Call · run_arc_fit_diagnostic
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "run_arc_fit_diagnostic",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
2 D2 node
Arc Paymaster Economics Model art-46-arc-paymaster-model
paymaster_verdict, sponsorship_breakeven feed Stage 3 CPN economics
MCP Call · model_arc_paymaster_economics
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "model_arc_paymaster_economics",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
3 TERMINAL · D3 node
Arc CPN Corridor Economics Model art-43-arc-cpn-model
npv_3yr, cost_per_payment — Exports agentic commerce mandate — final stage
MCP Call · model_arc_cpn_economics
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "model_arc_cpn_economics",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
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: Our checkout agents generate thousands of small gas claims each month. At what ether gas price does the paymaster case collapse?
Run the AINumbers MCP tool `run_chain` with {"chain":"arc-agentic-commerce"} and read `art-46-arc-paymaster-model.verdict`.
Re-run with `inputs` for `art-46-arc-paymaster-model`, reusing the values that result echoed, with `gas_price_gwei` set to 0.03. 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/arc-agentic-commerce.html