{"uid":"cap_uMJrzC4NKZOpqePiyYlnH","slug":"cross-protocol-payment-intent-routing-decision-procedure-3e5efdca","name":"Cross-protocol payment-intent routing decision procedure","description":"Decision procedure for an agent holding a payment intent that can be settled via multiple protocols: x402, AP2, or MPP. Covers protocol capability checks against the merchant offer, intent normalization across protocols, cost and latency comparison, scoped-account policy envelope checks (approved intent, policy expiry, spending caps) before routing, a single-routing rule so one intent is never double-settled across protocols, re-quote fallback, and receipt binding to the chosen protocol.","url":"https://k2so.wrong.systems/api/services/agent-payment-intent-and-authorization-governanc","method":"GET","headers":{},"bodySchema":{"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":"Cross-protocol payment-intent routing 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":{"type":"string"},"selfPay":{"type":"boolean"},"transaction":{"type":"string"}}},"service":{"type":"string"},"provider":{"type":"string","const":"K-2SO"}}}}}}},"responseSchema":{"type":"json","example":{"ok":true,"paid":true,"result":{"ok":true,"brief":"plain prose decision procedure (120+ words)","model":"deepseek/deepseek-v4-flash-0731","topic":"string topic","service":"agent-payment-intent-and-authorization-governanc","procedure":"same as brief","generatedAt":"2026-01-01T00:00:00.000Z","generationSource":"deterministic"},"service":"agent-payment-intent-and-authorization-governanc","provider":"K-2SO"}},"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.002","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"down","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.002/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.002","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.002","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_6mT7vkUwCyAzAnCjZ5sQW","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.002","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Returns a decision procedure for routing a payment intent across x402, AP2, or MPP protocols, including capability checks, cost/latency comparison, policy validation, and receipt binding.","exampleAgentPrompt":"I need a decision procedure for routing a payment intent — walk me through how to pick between x402, AP2, and MPP for a given merchant offer, including protocol capability checks, cost and latency comparison, spending cap policy validation, and how to bind the receipt once I've chosen.","exampleUseCases":[{"title":"Choosing protocol for merchant checkout","prompt":"My agent has a payment intent to settle a $12 purchase and the merchant supports x402 and AP2 — can you give me a step-by-step decision procedure for picking the right protocol, including cost and latency tradeoffs and how to make sure I don't double-settle?"},{"title":"Spending cap policy gate before payment routing","prompt":"Before my agent routes this payment intent, I need to check it against the scoped account's spending cap and policy expiry — can you give me the decision procedure to validate the intent is within policy before committing to a protocol?"},{"title":"Re-quote fallback after failed routing","prompt":"My agent's initial payment routing attempt failed and I need the fallback re-quote procedure — walk me through how to re-evaluate the merchant offer and pick a new protocol from x402, AP2, or MPP without accidentally settling the original intent twice."}],"resultDescription":"A structured decision procedure brief (prose and structured fields) covering: protocol capability checks against the merchant offer, intent normalization across x402/AP2/MPP, cost and latency comparison, scoped-account policy envelope validation (approved intent, policy expiry, spending caps), a single-routing rule to prevent double-settlement, re-quote fallback steps, and receipt binding instructions for the chosen protocol. Response includes ok/paid status, a generatedAt timestamp, model and generation source metadata.","failureModes":["Payment required but not provided — endpoint returns 402 with payment instructions","Invalid or missing query parameters return schema validation error","LLM or reasoning generation failure returns ok:false with error detail","Stale or expired decision procedure if merchant offer changes after generation","No protocol capability match found for the given merchant offer"],"whenToPreferThis":"Choose this endpoint when an agent holds a payment intent that could be settled via multiple protocols (x402, AP2, MPP) and needs a structured, policy-aware decision procedure — especially when spending cap enforcement, double-settlement prevention, and receipt binding are required. Prefer over generic payment routing when you need cross-protocol normalization and single-routing guarantees in one call.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-15T12:25:46.691Z","isFirstParty":false}