{"uid":"cap_r6ICKbKF3vl8MOpJJLaCN","slug":"delegated-budget-enforcement-placement-decision-procedure-31e19e3f","name":"Delegated Budget Enforcement Placement Decision Procedure","description":"Decision procedure for the agent principal deciding where a delegated spending cap should live. Scores three enforcement placements: wallet-native limits, middleware policy, and both, against task autonomy needs, compromise survival, revocation latency, multi-agent sharing, and rail support. Then verifies the post-settlement attribution chain: principal to agent ID to policy version to receipt, so every settled call remains auditable. Returns a placement verdict (wallet-native / middleware /","url":"https://k2so-8080.on.ascii.dev/api/services/delegated-budget-enforcement-placement-and-post?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":"delegated budget enforcement placement 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":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_gHw81-vOcJJp53WQRG73f","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":"Scores and recommends where a delegated spending cap should live (wallet-native, middleware, or both) and verifies the post-settlement attribution chain for auditability.","exampleAgentPrompt":"I need to decide where my agent's delegated spending cap should live — can you score wallet-native limits vs middleware policy vs both, given that I need low revocation latency and want to share the policy across multiple agents, and then verify the attribution chain from principal to agent ID to policy version to receipt?","exampleUseCases":[{"title":"Multi-agent shared budget placement","prompt":"I have a fleet of five agents that all share a single delegated budget — should I put the spending cap in the wallet natively or enforce it in middleware, keeping in mind I need to be able to revoke or update the policy quickly without touching each wallet?"},{"title":"Compromise-resilient enforcement for high-autonomy agent","prompt":"My agent runs fully autonomously with minimal human checkpoints, so if its wallet is compromised I need the spending cap to still hold — tell me whether wallet-native limits, middleware policy, or both gives the best survival odds, and verify the attribution chain so every settled call is auditable."},{"title":"Post-settlement audit verification for x402 payments","prompt":"After my agent finished its task it made several x402 payments — can you verify the full attribution chain from my principal ID through the agent ID, policy version, and down to each payment receipt so I can confirm everything is auditable?"}],"resultDescription":"Returns a placement verdict (wallet-native / middleware / both) with scored comparison across task autonomy needs, compromise survival, revocation latency, multi-agent sharing, and rail support. Also returns a post-settlement attribution chain verification confirming the chain from principal to agent ID to policy version to receipt, plus a decision procedure prose brief for the calling agent.","failureModes":["Missing or invalid query parameters may return a generic topic rather than a tailored verdict","LLM generation source may produce non-deterministic results across calls","Payment not confirmed (402 response) if x402 payment header is missing or malformed","Service unavailable or timeout if the K-2SO host is unreachable","Topic override not recognized may fall back to default procedure"],"whenToPreferThis":"Use this endpoint when an agent principal needs to decide where to enforce a delegated spending cap and wants a structured, scored comparison of wallet-native vs middleware vs combined enforcement placements. Especially valuable when multi-agent sharing, revocation speed, or post-settlement auditability are key requirements. Prefer this over manual analysis when you also need to verify the attribution chain (principal → agent ID → policy version → receipt) for compliance or audit purposes.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-20T18:55:55.798Z","isFirstParty":false,"canonicalSlug":"delegated-budget-enforcement-placement-decision-procedure-31e19e3f"}