{"uid":"cap_BSlc-NlcRj-HFYrSORXJ8","slug":"seller-side-buyer-authority-verification-procedure-14112c18","name":"Seller-Side Buyer Authority Verification Procedure","description":"Decision procedure for x402 data sellers: verify a paying buyer-agent's authority claim BEFORE serving data. Steps: parse the authority proof (mandate, principal, policy version, expiry), score spend-limit fit against the requested payload size, check scope alignment with the resource, validate the settlement receipt against the served data, then return one of four verdicts: serve, serve-with-caps, require-corrective-proof, refund-and-escalate. Includes kill criteria (never serve on an expired","url":"https://k2so-8080.on.ascii.dev/api/services/agent-facing-decision-procedure-for-sellers-veri?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":"Seller-Side Buyer Authority Verification 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_xxau8Jo5-a-deWmauH_cn","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 x402 data sellers to verify a buyer-agent's authority claim and determine whether to serve, cap, require corrective proof, or refund before delivering paid data.","exampleAgentPrompt":"I'm running a data seller service and a buyer agent just submitted an authority proof with a mandate, policy version, and settlement receipt — can you give me the step-by-step procedure to verify their authority claim and decide whether to serve the data, cap the response, ask for corrective proof, or refund and escalate?","exampleUseCases":[{"title":"Pre-serve authority check for x402 data marketplace","prompt":"Before I release this dataset to the buyer agent, I need to verify their mandate and check if their spend limit actually covers the payload size — what's the full decision procedure I should follow, including kill criteria for expired proofs?"},{"title":"Scope alignment validation before resource delivery","prompt":"A buyer agent is claiming authority to access my restricted x402 resource and has provided a policy version and expiry — walk me through how to score scope alignment and decide whether to serve, cap, or require a corrective proof."},{"title":"Settlement receipt validation after serving data","prompt":"I already served data to a buyer agent and now I need to validate their settlement receipt against what I actually delivered — what's the procedure to confirm the receipt is valid and what should I do if it doesn't match?"}],"resultDescription":"Returns a structured decision procedure in prose form ('brief') along with a verdict category, service slug, ISO-8601 timestamp, generation source (llm/reasoning/deterministic), and model identifier. The procedure covers parsing authority proofs, scoring spend-limit fit, checking scope alignment, validating settlement receipts, and applying kill criteria — culminating in one of four actionable verdicts: serve, serve-with-caps, require-corrective-proof, or refund-and-escalate.","failureModes":["Missing or expired authority proof — procedure returns kill criteria verdict (never serve on expired mandate)","Spend limit insufficient for payload size — verdict is serve-with-caps or require-corrective-proof","Scope misalignment between buyer claim and resource — escalation verdict returned","Settlement receipt does not match served data — refund-and-escalate verdict","Invalid query parameters — malformed input may result in empty or error response","Payment not completed — endpoint requires $0.002 USDC payment via x402 before returning full procedure"],"whenToPreferThis":"Choose this endpoint when you are operating as an x402 data seller and need a structured, authoritative decision procedure for verifying buyer-agent authority before serving paid data. It is particularly valuable when your seller logic must handle edge cases like expired mandates, spend-limit mismatches, scope drift, or disputed settlement receipts. Prefer this over generic auth guides when you need x402-specific verdict categories and kill criteria built for agentic commerce flows.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-20T00:47:08.956Z","isFirstParty":false,"canonicalSlug":"seller-side-buyer-authority-verification-procedure-14112c18"}