Single-node D0 diagnostic grading an agent platform/operator A-F across settlement rail, receipt & mandate, HNP autonomy, reconciliation, metering, and runtime fraud for the agent-economy runtime layer; routes to the right Wave-14 aer-* chain.
run_agent_economy_fit{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "run_agent_economy_fit",
"arguments": {}
},
"id": 1
}
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: The readiness diagnostic scored our agent runtime. If we adopt the x402 V2 rail, how far does the score climb?
Run the AINumbers MCP tool `run_chain` with {"chain":"agent-economy-fit"} and read `art-60-agent-economy-runtime-fit-diagnostic.overall_score`.
Re-run with `inputs` for `art-60-agent-economy-runtime-fit-diagnostic`, reusing the values that result echoed, with `settlement_protocol` set to "x402-v2". 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-fit.html