OpenChainGraph Suite · Agentic Commerce

Agentic Commerce Convergence

Note (dated 2026-08-06): 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.

Binds one agent-run transaction across three independent agentic-commerce layers into a single hash-anchored composite: UCP cart/checkout discovery, ACP checkout conformance, and the AP2 payment mandate. UCP composes with AP2 rather than competing with it (Google developer blog); this chain evidences that composition as one dated receipt. Each step keeps its own verdict scope, never merged into a single cross-layer determination.

OpenChainGraph · 3 Steps compliance mandate Hash-Anchored chain_depth:3 Client-Side · Zero PII
Chain Topology: Agentic Commerce Convergence
Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 3 Steps
1 ROOT node
UCP Checkout Payload Lint art-564-ucp-checkout-payload-lint
Produces UCP cart/checkout resource conformance (CONFORMANT / NONCONFORMANT / UNKNOWN_VERSION) against the pinned v2026-04-08 schema, evidencing the discovery/cart layer of this declared transaction; each step keeps its own verdict scope, never merged into a single cross-layer determination
MCP Call · lint_ucp_checkout_payload
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "lint_ucp_checkout_payload",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
2 D2 node
ACP Checkout Conformance Validator art-12-acp-checkout-conformance-validator
Produces ACP checkout-session conformance findings over the same caller-declared amount/currency/merchant identity fields, evidencing the checkout layer of this declared transaction
MCP Call · validate_acp_checkout
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "validate_acp_checkout",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
3 TERMINAL node
AP2 Mandate-Chain Validator art-01-ap2-mandate-chain-validator
AP2 mandate-chain integrity determination over the same caller-declared amount/currency/merchant identity fields, closing the composite as the payment-authorization layer; terminal stage
MCP Call · validate_ap2_mandate_chain
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "validate_ap2_mandate_chain",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
▶ Run this chain (live) browser · real execution · composite §4 hash
Export Artifacts
Download the 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: We lint one checkout payload across UCP and ACP. What happens to the UCP verdict when the totals block goes missing?
Run the AINumbers MCP tool `run_chain` with {"chain":"agentic-commerce-convergence"} and read `art-564-ucp-checkout-payload-lint.verdict`.
Re-run with `inputs` for `art-564-ucp-checkout-payload-lint`, reusing the values that result echoed, with `payload` changed so its totals block is missing. 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/agentic-commerce-convergence.html