{"uid":"cap_BCDSkE_wjcB_AhpowJTUl","slug":"virtual-wallet-merchant-allowlist-governance-procedure-b7aafd7b","name":"Virtual Wallet Merchant Allowlist Governance Procedure","description":"Decision procedure for an agent governing which merchants may debit a virtual agent wallet. Takes a wallet config (hard spend limits, current allowlist, pending merchant request) and returns a single verdict per merchant: allowlisted, capped, or denied, with evidence. Steps: verify merchant identity anchor and payTo address match, check per-merchant and aggregate caps against the hard limit, validate the merchant's x402 challenge surface answers 402 instead of 404/405, record add/revoke actions","url":"https://k2so-8080.on.ascii.dev/api/services/decision-procedure-for-an-agent-governing-a-merc?utm_source=zero.xyz","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":"Virtual wallet merchant allowlist governance 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":null,"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":"unknown","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_nEq3MopWY2IrUnOMzWCrv","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 per-merchant verdict (allowlisted, capped, or denied) for governing which merchants may debit a virtual agent wallet, with identity verification, cap checks, and x402 challenge surface validation.","exampleAgentPrompt":"I have a pending merchant request from 'ShopBot Pro' wanting to debit my agent wallet — run the governance procedure against my current allowlist with a hard limit of $50 and tell me whether to allowlist, cap, or deny them based on their identity anchor and x402 challenge surface check.","exampleUseCases":[{"title":"Onboarding new merchant to agent wallet","prompt":"There's a new merchant called 'DataFeed Inc' requesting access to debit my virtual agent wallet. My hard spend limit is $20 per merchant. Can you run the allowlist governance procedure to verify their identity anchor and payTo address, check their x402 challenge surface, and give me a verdict on whether to add them to my allowlist?"},{"title":"Enforcing per-merchant spend caps","prompt":"My agent wallet allowlist already has three merchants. 'MediaBot' has been debiting heavily and I want to know if they've hit their per-merchant cap relative to my $100 aggregate hard limit — run the governance procedure and tell me if they should be capped or stay allowlisted."},{"title":"Revoking a suspicious merchant","prompt":"I think 'QuickCharge LLC' in my agent wallet allowlist might have changed their payTo address — can you run the governance decision procedure to re-verify their identity anchor against the current payTo address and let me know if I should revoke their allowlist status?"}],"resultDescription":"A structured verdict for the pending merchant request: one of 'allowlisted', 'capped', or 'denied', accompanied by evidence covering identity anchor and payTo address match status, per-merchant and aggregate cap compliance, x402 challenge surface validation result, and a record of any add/revoke actions taken.","failureModes":["Merchant identity anchor does not match payTo address — verdict: denied with mismatch evidence","x402 challenge surface returns 404 or 405 instead of 402 — merchant fails surface validation","Aggregate cap would be exceeded by adding merchant — verdict: capped or denied","Malformed wallet config input causes handler error (ok: false)","Network timeout reaching the decision procedure endpoint","Missing required fields in wallet config result in validation error"],"whenToPreferThis":"Use this endpoint when an autonomous agent needs a structured, evidence-backed governance decision about whether to allowlist, cap, or deny a merchant before granting them debit access to a virtual agent wallet. It is specifically designed for x402-based payment flows where merchant identity verification, spend cap enforcement, and challenge surface validation must all be combined into a single policy verdict. Prefer this over ad-hoc rule checks when you need an auditable, single-call decision with recorded add/revoke actions.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-22T06:37:41.994Z","isFirstParty":false,"canonicalSlug":"virtual-wallet-merchant-allowlist-governance-procedure-b7aafd7b"}