{"uid":"cap_SKJiTYRo6-h4y7mDkOrB2","slug":"payperbyte-sanctions-screening-oracle-71aa1963","name":"PayPerByte Sanctions Screening Oracle","description":"Know-Your-Agent counterparty screening — sanctions pillar. Signed OFAC SDN + Consolidated screen on an address or name, pinned to the exact list-state (date + sha256). Screens the counterparty you supply — not the calling agent's identity. Full scope: https://x402.payperbyte.io/feeds","url":"https://x402.payperbyte.io/feeds/sanctions-screen","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"name":{"type":"string","maxLength":256,"minLength":2,"description":"Counterparty name (individual or entity). Screened exact + conservative fuzzy against primary and a.k.a. names in the SDN + Consolidated lists."},"chain":{"type":"string","description":"Optional, informational only — the SDN annex pins addresses to currency symbols; chain never gates a hit."},"address":{"type":"string","description":"Counterparty address: 0x+40-hex (EVM) or a digital-currency address. Checked against the OFAC SDN digital-currency annex."}}},"responseSchema":{"type":"json","example":{"_note":"Excerpt of a real answer (live service, 2026-07-01); hash/signature elided, signals/consolidated trimmed. Every answer pins the exact OFAC list version (published date + sha256 + entry count) it was judged against. Screening signal, not legal advice. The EIP-712 receipt — domain chainId 421614 = Arbitrum Sepolia, a frozen signing namespace, not a settlement rail — proves who signed these exact bytes (authenticity + tamper-evidence), not that the screening result is correct. Recompute keccak256(canonical answer bytes) and recover the signer before acting.","answer":{"v":"sanctions-screen/v1","query":{"name":"Lazarus Group","chain":null,"address":null},"score":0,"reasons":["name exactly matches OFAC SDN primary name \"LAZARUS GROUP\": entry #27307 \"LAZARUS GROUP\" [DPRK3] — list published 2026-06-30"],"verdict":"BLOCK","list_state":{"sdn":{"stale":false,"source":"OFAC SDN (Specially Designated Nationals and Blocked Persons)","entry_count":19129,"content_sha256":"a04efa5d60104ebd35fc08b6891811120d151bf37801fbd3c01e64380198f099","published_date":"2026-06-30"}},"methodology":"ss-v1"},"attestation":{"domain":{"name":"BYTE Library","chainId":421614,"version":"1","verifyingContract":"0x44729bB148F46d8Db509E47b0453edc271e06e95"},"signer":"0x344ECaCDe6566294c31397445c98b62a3EEEA456","signature":"0x…","payloadHash":"0x…"}}},"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.1","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.1/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.1","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.1","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_mlKB32hvOD90lssBDUHg3","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.1","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Screens a crypto address or counterparty name against OFAC SDN and Consolidated sanctions lists, returning a BLOCK/PASS verdict with EIP-712 cryptographic attestation","exampleAgentPrompt":"Before I send funds, can you screen the wallet address 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 against the OFAC sanctions list and give me a signed attestation I can verify?","exampleUseCases":[{"title":"Pre-payment DeFi compliance check","prompt":"I'm about to send 50,000 USDC to 0x1da5821544e25c636c1417ba96ade4cf6d2f9b5a on Ethereum — can you screen that address against OFAC sanctions first and give me the signed verdict before I proceed?"},{"title":"Counterparty name sanctions screening","prompt":"We're onboarding a new business partner called 'Lazarus Group' — can you run their name through the OFAC SDN list and send me back the verdict with the cryptographic proof so our compliance team can log it?"},{"title":"Automated wallet blacklist check for a dApp","prompt":"My app needs to block sanctioned users — can you check if the address 0x7F367cC41522cE07553e823bf3be79A889debe1B is on the OFAC sanctions list and return the attested result with the list version details?"}],"resultDescription":"A JSON object containing: a verdict field (BLOCK or PASS), a score, an array of reasons explaining any match (including the exact SDN entry number and list name), the exact OFAC list state screened against (source, published date, SHA-256 content hash, entry count, staleness flag), the methodology version, and an EIP-712 attestation block with the signer address, signature, payload hash, and domain details (chainId 421614 = Arbitrum Sepolia signing namespace). The signer can be recovered from the attestation to verify authenticity and tamper-evidence.","failureModes":["Missing both address and name fields — API returns 400 requiring at least one of address or name","Invalid address format (not 0x+40-hex or recognized digital-currency format) — rejected at input validation","Payment failure via x402 protocol — endpoint returns 402 Payment Required if USDC payment is not attached","OFAC list temporarily stale — stale:true flag in list_state indicates the list could not be refreshed","Attestation signer mismatch — if recovered signer does not match expected publisher key, data may be tampered","Name with fewer than 2 characters or more than 256 characters — rejected by minLength/maxLength constraints"],"whenToPreferThis":"Choose this endpoint when you need a cryptographically attested, verifiable sanctions verdict that you can independently verify on-chain — not just a raw database query. It is ideal for DeFi applications, payment agents, and compliance workflows that require tamper-evident proof of which exact OFAC list version (SHA-256 anchored) was consulted and that the result was signed by the feed's own publisher key. Prefer this over generic sanctions APIs when you need EIP-712 receipts for audit trails, on-chain verifiability, or when operating in trustless agent pipelines where data provenance must be cryptographically proven rather than assumed.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-13T18:48:35.569Z","isFirstParty":false}