{"uid":"cap_Mwk5PbcjUz1vMF3LVlxaW","slug":"hcrb-in-evm-address-sanctions-screener-c22e707c","name":"hcrb.in EVM Address Sanctions Screener","description":"Exact EVM-address comparison against the identified address snapshot and existing operator block policy. Current legal status is unknown; is_sanctioned is null. valid=false preserves a local block; valid=null never authorizes a transaction. Names are not screened. Missing, stale or incomplete evidence is explicit; no UN/EU coverage or sanctions clearance is provided.","url":"https://hcrb.in/v1/tools/sanctions-address-screen/call?utm_source=zero.xyz","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"input":{"type":"object","required":["subject"],"properties":{"subject":{"type":"string","description":"EVM address (0x...) or ISO 3166-1 country code / jurisdiction name"}}}}},"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.015","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.005/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.005","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.005","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_dg7rsK11kOu2hUoUlN2ZP","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.005","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Checks an EVM wallet address or jurisdiction against an identified-address snapshot and operator block policy to determine sanctions exposure","exampleAgentPrompt":"Before I send USDC to 0x742d35Cc6634C0532925a3b8D4C9C6F1b2e3A4f5, can you do a sanctions screen on that wallet address to check if it's blocked or flagged?","exampleUseCases":[{"title":"Pre-payment wallet compliance check","prompt":"I'm about to pay a contractor at 0xAbC123def456...7890 — can you run a sanctions screen on that address to make sure it's not blocked before I transfer funds?"},{"title":"DeFi protocol counterparty screening","prompt":"Screen the address 0x1234567890abcdef1234567890abcdef12345678 against sanctions lists and tell me if your operator block policy has flagged it — I need to know if it's safe to interact with."},{"title":"Jurisdiction-level sanctions check","prompt":"Can you check whether Iran is currently subject to sanctions in your coverage? I want to know the legal status before onboarding any counterparties from that jurisdiction."}],"resultDescription":"Returns a JSON object with: a valid boolean (false means a local block is preserved, null means authorization was never granted), an is_sanctioned field (null when legal status is unknown), evidence completeness flags indicating whether data is missing or stale, and a note that UN/EU coverage and full sanctions clearance are not provided. The result reflects an exact EVM-address snapshot comparison plus operator block policy.","failureModes":["Input address not in 0x... EVM format — schema validation error","Stale snapshot data — evidence flagged as incomplete or missing","is_sanctioned returns null — legal status genuinely unknown, not a clearance","valid returns null — means authorization was never granted, not that address is clean","No UN or EU sanctions database coverage — endpoint does not provide full international clearance","Names (not addresses) are not screened by this endpoint"],"whenToPreferThis":"Use this endpoint when you need a fast, deterministic, per-address sanctions pre-check for EVM wallets before executing on-chain transactions or payments. It is best suited for agent pipelines that require a binary block/allow signal based on an operator-maintained snapshot plus block policy, and where the cost of a false negative is mitigated by downstream compliance layers. Prefer this over broader KYC services when you only need address-level screening (not name or entity screening) on EVM-compatible chains. Do not rely on it as a sole compliance gate for jurisdictions requiring UN or EU sanctions coverage.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-31T00:30:55.006Z","isFirstParty":false,"canonicalSlug":"hcrb-in-evm-address-sanctions-screener-c22e707c"}