Agent-Service Marketplace Onboarding & Metering

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.

Reading mode (RUNBOOK): Run these steps in order. A marketplace operator really does verify an agent’s identity, then apply the acceptance policy, then configure metering, before a listing goes live.

W-F. Agent identity & authorization attestation (art-04) -> agent-traffic acceptance policy (art-21) -> service metering/pricing (ART-63). Onboards an agent service into a micropayment marketplace with a metered, policy-gated listing.

OpenChainGraph · 3 Steps payment policy Hash-Anchored §4 chain_depth:3 Client-Side · Zero PII

Chain Stages · 3 Steps

1 ROOT · D0 node

Agent Identity & Authorization Attestation Checker art-04-agent-identity-attestation-checker

attestation verdict (H1) feeds the traffic-policy builder

MCP Call · check_agent_attestation

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

↓

2 D2 node

Agent-Traffic Acceptance Policy Builder art-21-agent-traffic-acceptance-policy-builder

acceptance policy (H2) feeds the metering modeler

MCP Call · build_agent_traffic_policy

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

↓

3 TERMINAL · D3 node

Agent-Service Metering & Marketplace Economics Modeler art-63-agent-service-metering-modeler

Exports composite marketplace artifact with execution_hash (H3), final stage

MCP Call · model_agent_service_metering

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

Question: Our marketplace is drafting its acceptance limits for agent traffic. Does a five-thousand-dollar single-transaction cap still read as sound policy? Run the AINumbers MCP tool `run_chain` with {"chain":"agent-economy-marketplace"} and read `art-21-agent-traffic-acceptance-policy-builder.verdict`. Re-run with `inputs` for `art-21-agent-traffic-acceptance-policy-builder`, reusing the values that result echoed, with `max_single_val_usd` set to 5000. 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-marketplace.html

Agent-Service Marketplace Onboarding & Metering

Ask your agent