{"uid":"cap_GtXrssObsthLueuovl29y","slug":"paid-tool-request-scoping-and-receipt-binding-standard-dd7d0b84","name":"Paid Tool Request Scoping and Receipt Binding Standard","description":"Checkable procedure for an agent to scope any paid tool call into a minimal request envelope with bounded result size and explicit deliverable, then bind the expected receipt to that request before approving spend. Includes kill criteria for ambiguous or unbounded merchant responses and a verification step after settlement.","url":"https://k2so.wrong.systems/api/services/agent-paid-tool-request-scoping-receipt-binding","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":"Paid tool request scoping and receipt binding standard 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-paid-tool-request-scoping-receipt-binding","procedure":"same as brief","generatedAt":"2026-01-01T00:00:00.000Z","generationSource":"deterministic"},"service":"agent-paid-tool-request-scoping-receipt-binding","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_k4qTPAB6mhrOqvW5zR9NQ","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 scoping paid tool calls into minimal bounded request envelopes and binding expected receipts before approving spend, with kill criteria and post-settlement verification.","exampleAgentPrompt":"Walk me through the standard procedure for scoping a paid GET tool call into a minimal bounded request before I approve the spend, and tell me exactly how to bind and verify the receipt afterward.","exampleUseCases":[{"title":"Pre-approval spend gate for agent tool call","prompt":"Before my agent calls that paid data API, what's the step-by-step procedure to scope the request into a minimal envelope, cap the response size, and bind the expected receipt so I don't approve an open-ended charge?"},{"title":"Kill criteria for ambiguous merchant response","prompt":"My agent got back an unclear or unbounded response from a paid merchant API — what are the kill criteria it should apply, and when should it refuse to settle the payment?"},{"title":"Post-settlement receipt verification workflow","prompt":"My agent just completed a paid x402 tool call — walk me through the verification steps it should follow to confirm the receipt matches what was expected before marking the transaction as complete."}],"resultDescription":"A structured JSON object containing a prose decision procedure (brief) for the agent, the topic and service slug, a generation source indicator (llm, reasoning, or deterministic), an ISO-8601 timestamp, and payment metadata including transaction reference and payer details. The brief describes the full scoping, receipt-binding, kill-criteria, and post-settlement verification workflow.","failureModes":["Missing or malformed input type/method fields returns a validation error","Ambiguous topic override may produce a generic rather than specific procedure","LLM generation source may produce non-deterministic results across calls","Payment not confirmed (paid: false) results in no procedure being returned","Network timeout if the backing generation service is slow","Incorrect HTTP method (e.g. POST instead of GET) returns method-not-allowed"],"whenToPreferThis":"Choose this endpoint when an autonomous agent needs a standardized, checkable procedure for safely scoping and approving any paid tool call — especially when working with x402 micropayments, unknown merchant response sizes, or when building spend-control guardrails. Prefer this over ad-hoc logic when you need explicit kill criteria for ambiguous responses and a post-settlement verification protocol baked in.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-15T11:25:10.108Z","isFirstParty":false}