{"uid":"cap_Rhk9o9X9rMWT1orH7EhiX","slug":"x402-settlement-recipient-check-97b3d39d","name":"X402 Settlement Recipient Check","description":"X402 Settlement Recipient Check: X402 Settlement Recipient Check compares settlement recipient with the accepted pay-to address from bounded caller-supplied values without an external provider. Call X402 Settlement Recipient Check before paying for or accepting an x402 or agent delivery assembled from caller-supplied challenge and result metadata. Returns contract-specific checks, normalized evidence, mismatch reasons, and an explicit acceptance or rejection status for X402 Settlement Recipient…","url":"https://api.delx.ai/api/v1/x402/x402-settlement-recipient-check?utm_source=zero.xyz","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"pay_to":{"type":"string","maxLength":8192,"description":"Pay To supplied to X402 Settlement Recipient Check; used only for this bounded calculation and processed in memory without retention."},"recipient":{"type":"string","maxLength":8192,"description":"Recipient supplied to X402 Settlement Recipient Check; used only for this bounded calculation and processed in memory without retention."}}},"responseSchema":{"type":"json","example":{"result":{"actual":"0x1111111111111111111111111111111111111111","matched":true,"expected":"0x1111111111111111111111111111111111111111"},"schema":"delx/util-x402-settlement-recipient-check/v1","status":"pass","evidence":{"retained":false,"input_sha256":"e670f19cbdd7aaae3edbde715feff65196c9b5cafb580a8d0d7ef09720d6cffa","external_calls":0},"operation":"delivery_contract:x402_settlement_recipient_check"}},"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.001","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.001/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.001","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.001","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_JGzRDtJPGtA6U38BftVAZ","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.001","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Validates that an x402 payment settlement recipient matches the expected pay-to address, returning acceptance/rejection status and mismatch reasons.","exampleAgentPrompt":"Before we accept this x402 payment, can you check whether the settlement recipient matches the pay-to address — pay_to is '0xAbC123...' and the recipient is '0xDef456...' — and tell me if there's a mismatch or if it's safe to proceed?","exampleUseCases":[{"title":"Guard against wrong pay-to in agent delivery","prompt":"We're about to finalize an x402 agent delivery — the pay_to from the challenge is '0x1234abcd...' and the recipient in the result metadata is '0x5678efgh...'. Can you verify these match before we release payment?"},{"title":"Fraud check before x402 transaction","prompt":"I have an incoming x402 payment request where pay_to is '0xAAA111...' and the claimed recipient is '0xBBB222...'. Run a recipient check and tell me if these are consistent or if something looks off."},{"title":"Automated x402 settlement validation in payment pipeline","prompt":"In our payment pipeline, the x402 challenge says pay_to is '0xMerchant42...' but the settlement result shows recipient '0xMerchant42...'. Confirm the recipient check passes so we can mark this payment accepted."}],"resultDescription":"Returns an explicit acceptance or rejection status, contract-specific validation checks, normalized evidence from the provided addresses, and detailed mismatch reasons explaining any discrepancy between the pay_to and recipient values.","failureModes":["Missing or empty pay_to or recipient fields — validation cannot run without both values","Addresses exceed maxLength of 8192 characters — request rejected","Malformed address strings that cannot be parsed or normalized","Network or service error returning 5xx — retry recommended","Mismatch detected between pay_to and recipient — returns rejection status with specific mismatch reasons"],"whenToPreferThis":"Use this endpoint whenever you need to verify x402 payment settlement integrity before accepting or executing a payment, particularly in agentic pipelines where challenge and result metadata come from caller-supplied or untrusted sources. It performs the check in-memory without external calls or data retention, making it suitable for security-sensitive pre-payment validation. Prefer this over manual address comparison when you need structured rejection evidence and normalized output.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-22T06:49:36.648Z","isFirstParty":false,"canonicalSlug":"x402-settlement-recipient-check-97b3d39d"}