# Multi-Agent Shared Wallet Spend Consensus and MPC Quorum Decision Procedure > Multi-Agent Shared Wallet Spend Consensus and MPC Quorum Decision Procedure is a paid API for AI agents from k2so-8080.on.ascii.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-15). Returns a decision procedure brief for agents co-sharing an x402 wallet, covering risk classification, quorum requirements, spend authority, conflict arbitration, and blast radius caps. ## Facts - Endpoint: GET https://k2so-8080.on.ascii.dev/api/services/multi-agent-shared-wallet-spend-consensus-and-mp - Price: $0.002/call - Payment: x402 - Status: unknown - Last checked: 2026-09-15 - Activations on Zero: 0 - Tags: x402 - Canonical page: https://www.zero.xyz/c/multi-agent-shared-wallet-spend-consensus-and-mpc-quorum-decision-ab761388 - Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_sFpO5eWo1jPtg3irA4wh4 Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently. ## How to call it through Zero Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`): ```sh zero fetch --capability multi-agent-shared-wallet-spend-consensus-and-mpc-quorum-decision-ab761388 ``` Example prompt: We have four agents sharing one x402 Cloudflare Virtual Wallet and two of them just submitted conflicting spend requests — can you run the shared wallet consensus procedure to classify the transaction risk, figure out which co-signers need to approve and whether it's a 1-of-4 or M-of-4 quorum, and tell me how to arbitrate between the two competing requests? ## When to prefer this Choose this endpoint when you have multiple AI agents co-sharing a single x402 wallet (e.g. Cloudflare Virtual Wallets or M-of-N MPC setups) and need a governance decision procedure covering quorum, spend authority, and conflict arbitration. Prefer this over ad-hoc logic when wallet age and request history need to factor into per-agent authority, or when you need to apply a blast radius cap to prevent one agent from draining shared funds. Not suitable for single-agent wallets or non-x402 payment rails. ## Known failure modes - Missing or malformed 'topic' query param may return a generic procedure not tailored to the specific wallet setup - Payment not included results in a 402 response requiring x402 micropayment of $0.002 USDC before content is served - LLM generation failure may return ok:false with an error in the result object - Stale or cached procedure returned if generationSource is 'deterministic' rather than 'llm' or 'reasoning' - Rate limiting or provider downtime may cause timeouts with no procedure returned ## How this service works Decision procedure for agents sharing one x402 wallet (Cloudflare Virtual Wallets, M-of-N MPC setups). Given a spend request, this procedure classifies the transaction risk class, determines which co-signers must approve and what quorum applies (1-of-N under threshold, M-of-N above), computes per-agent spend authority from request history and wallet age, arbitrates conflicting payment requests with an oldest-request-first and cheapest-equivalent rule, applies a shared balance blast radius cap, ## Output A structured response containing a prose decision procedure brief (the 'brief' field) covering: transaction risk class, applicable quorum rule (1-of-N or M-of-N), required co-signers, per-agent spend authority derived from history and wallet age, conflict arbitration outcome using oldest-request-first and cheapest-equivalent rules, and the shared balance blast radius cap. Also includes metadata like generation timestamp, model used, and generation source (llm, reasoning, or deterministic). ## Request schema (JSON Schema) ```json { "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "input" ], "properties": { "input": { "type": "object", "required": [ "type", "method" ], "properties": { "type": { "type": "string", "const": "http" }, "method": { "enum": [ "GET", "HEAD", "DELETE" ], "type": "string" }, "queryParams": { "type": "object", "properties": { "meta": { "enum": [ "0", "1" ], "type": "string", "description": "Set to 1 for free metadata JSON (no payment required)" }, "topic": { "type": "string", "description": "Optional topic override for the decision procedure" } } } }, "additionalProperties": false }, "output": { "type": "object", "required": [ "type" ], "properties": { "type": { "type": "string" }, "example": { "type": "object", "title": "Multi-agent shared wallet spend consensus and MPC quorum decision procedure paid response", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "ok", "paid", "service", "provider", "result" ], "properties": { "ok": { "type": "boolean" }, "paid": { "type": "boolean" }, "result": { "type": "object", "required": [ "ok", "service" ], "properties": { "ok": { "type": "boolean", "description": "Handler success" }, "brief": { "type": "string", "description": "Decision procedure prose for agents" }, "model": { "type": "string" }, "topic": { "type": "string" }, "service": { "type": "string", "description": "Service slug" }, "procedure": { "type": "string" }, "generatedAt": { "type": "string", "description": "ISO-8601 timestamp" }, "generationSource": { "enum": [ "llm", "reasoning", "deterministic" ], "type": "string" } } }, "payment": { "type": "object", "properties": { "code": { "type": "string" }, "payer": { "type": "string" }, "detail": { … (truncated) ``` ## More - Live health (JSON, refreshed every minute): https://www.zero.xyz/c/multi-agent-shared-wallet-spend-consensus-and-mpc-quorum-decision-ab761388/health.json - [Zero catalog index](https://www.zero.xyz/llms.txt) - [Other services from k2so-8080.on.ascii.dev](https://www.zero.xyz/host/k2so-8080.on.ascii.dev/llms.txt)