{"uid":"cap_ybEYJhMpAf6EJnb12Q1QG","slug":"agent-wallet-control-precedence-schema-01ff33ae","name":"Agent Wallet Control Precedence Schema","description":"Deterministic procedure for resolving simultaneous bindings of merchant caps, per-period caps, fleet policy, single-transaction ceilings and category limits on one agent payment. Inputs include effective control set, limit values, binding scope, authorization authority, and transaction amount. Thresholds define when a control is exhausted, when overrides escalate, and when payment is rejected. Failure modes include ambiguous precedence rank, conflicting fleet and per-agent limits, stale cap","url":"https://k2so-8080.on.ascii.dev/api/services/agent-wallet-control-precedence-schema?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":"Agent wallet control precedence schema 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_DY2NMJUEnbNnR4dsqDKYJ","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 deterministic decision procedure for resolving conflicting wallet control limits (merchant caps, per-period caps, fleet policy, transaction ceilings, category limits) on a single agent payment.","exampleAgentPrompt":"I need the decision procedure for figuring out which spending control takes precedence when a fleet policy limit and a per-agent per-period cap are both active on the same payment — can you pull the agent wallet control precedence schema?","exampleUseCases":[{"title":"Fleet vs per-agent limit conflict resolution","prompt":"My agent fleet has a $500 fleet-wide daily cap and each agent also has a $100 per-period cap — when both are active on the same transaction, which one wins and how should the agent decide whether to reject or escalate the payment?"},{"title":"Category limit exhaustion check before payment","prompt":"Before my agent submits a payment in the 'software subscriptions' category, I need it to know exactly when a category limit is considered exhausted versus when it should escalate for override — can you get me the control precedence procedure for that?"},{"title":"Merchant cap vs transaction ceiling adjudication","prompt":"My agent is about to process a payment where both a merchant-specific cap and a single-transaction ceiling apply simultaneously — what is the correct order of precedence for resolving those two controls so the agent knows whether to proceed or reject?"}],"resultDescription":"A structured decision procedure document (prose brief plus optional procedure text) describing exactly how to rank and resolve simultaneous wallet control bindings — including threshold rules for control exhaustion, escalation triggers, and payment rejection criteria — along with metadata like generation source, timestamp, topic, and service slug.","failureModes":["Ambiguous precedence rank when two controls have equal priority — procedure may return an unresolvable conflict state","Conflicting fleet and per-agent limits with no defined override authority — escalation path undefined","Stale cap values provided — procedure may return outdated thresholds that don't reflect current authorization state","Invalid or missing topic override — falls back to default decision procedure scope","Payment metadata flag misuse — calling without ?meta=1 incurs charge even for schema-only queries"],"whenToPreferThis":"Use this endpoint when an AI agent must autonomously resolve competing wallet spending controls before authorizing or rejecting a payment, especially in multi-policy environments (fleet + merchant + category + period caps all active). Prefer this over manual policy lookup when the agent needs a single authoritative ranked procedure rather than raw policy documents.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-22T13:20:30.654Z","isFirstParty":false,"canonicalSlug":"agent-wallet-control-precedence-schema-01ff33ae"}