# Base Batch Address Screen (x402) > Base Batch Address Screen (x402) is a paid API for AI agents from api.x402risk.com, paid per call via x402, $0.08/call, status unknown (last checked 2026-10-02). Screens up to 25 Base EVM addresses in a single call against the OFAC SDN list and flags lookalike/address-poisoning matches, returning a verdict per address. ## Facts - Endpoint: POST https://api.x402risk.com/v1/address-screen/batch?utm_source=zero.xyz - Price: $0.08/call - Payment: x402 - Status: unknown - Last checked: 2026-10-02 - Activations on Zero: 0 - Tags: x402 - Canonical page: https://www.zero.xyz/c/base-batch-address-screen-x402-aa5fc224 - Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PrGOLg3c0PlcCFyNj_MrM Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently. ## How to call it through Zero Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`): ```sh zero fetch --capability base-batch-address-screen-x402-aa5fc224 -d '' ``` Example prompt: Before I send payments to these five Base addresses — 0x1234...abcd, 0xabcd...1234, 0xdeadbeef...etc — can you batch screen all of them for OFAC sanctions and address-poisoning risks, and flag any that should be blocked? ## When to prefer this Use this batch endpoint (POST /v1/address-screen/batch) when you need to screen multiple addresses simultaneously — it's more cost-efficient ($0.08 for up to 25 vs $0.005 each individually at scale) and reduces API round-trips. Prefer it over the single address-screen endpoint when processing payroll batches, exchange deposits, or any workflow with 2+ addresses. Use the token risk check endpoints instead when screening ERC-20 contract addresses for honeypot/rug-pull risk rather than sanctions compliance. ## Known failure modes - 400 error with no charge if any address in the batch is not a valid 0x EVM address format - 400 if addresses array is empty or exceeds 25 items - compare_to address format invalid returns 400 - Network or RPC errors may cause partial results with errors array populated per address - OFAC list may be as-of a specific list_date and not real-time; non-match does not guarantee compliance ## How this service works Pay-per-call token risk check for Base: send a Base ERC-20 contract address, get deterministic JSON risk flags (owner/renounced, upgradeable proxy, mint/pause/blacklist/fee functions, on-chain Uniswap v2/v3 + Aerodrome liquidity, holder concentration) and a rule-based risk_level. Use before buying or listing an unfamiliar Base token. $0.01 USDC. Invalid input returns 400 and is not charged. Not financial advice. Also: POST /v1/pretrade-check ($0.02) pre-trade sellability / honeypot simulation; POST /v1/address-screen ($0.005) pay-to address screen (OFAC SDN exact match, lookalike). Contact: agent-4610161f6fd5c36a@agentmail.to ## Output A JSON object with a count and a results array containing one entry per submitted address. Each entry includes: chain, address, verdict (block/allow/review), sanctioned boolean, OFAC SDN match details (program, entity name, SDN UID, list date), lookalike detection result, on-chain activity summary (tx count, first seen age), contract metadata, and a disclaimer. Cached and error fields are also included per address. ## Request schema (JSON Schema) ```json { "type": "object", "properties": { "addresses": { "type": "array", "items": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$", "description": "EVM address to screen (Base, chain 8453)" }, "maxItems": 25, "minItems": 1 }, "compare_to": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$", "description": "Optional intended recipient address; flags a lookalike (address-poisoning) match" } } } ``` ## Response schema (JSON Schema) ```json { "type": "json", "example": { "count": 1, "results": [ { "chain": "base", "cached": false, "errors": [], "labels": [], "status": "ok", "address": "0x098B716B8Aaf21512996dC57EB0615e2383E2f96", "product": "address-screen", "reasons": [ "exact match to an OFAC SDN digital currency address (LAZARUS GROUP; list date 2026-09-23)" ], "sources": [ "ofac-sdn", "base-rpc", "blockscout" ], "verdict": "block", "activity": { "tx_count_indexed": 0, "outgoing_tx_count": 0, "first_seen_age_days": 798.4, "first_seen_is_lower_bound": false }, "chain_id": 8453, "contract": null, "lookalike": null, "sanctions": { "list": "OFAC SDN (Specially Designated Nationals) - digital currency addresses", "matches": [ { "sdn_uid": "23036", "programs": [ "DPRK3" ], "sdn_name": "LAZARUS GROUP", "sdn_type": "Entity", "currency_tag": "ETH" } ], "list_date": "2026-09-23", "sanctioned": true }, "disclaimer": "Screening aid only, not a compliance clearance or legal advice. Sanctions result is an exact match against EVM-format digital currency addresses published in the OFAC SDN list as of list_date; a non-match does not mean an address or its owner is not sanctioned or is safe. On-chain facts and labels come from public sources and can be incomplete.", "sanctioned": true, "is_contract": false, "block_number": 35000000, "schema_version": "1.0", "eip7702_delegated_eoa": false } ], "disclaimer": "Screening aid only, not a compliance clearance or legal advice. Sanctions result is an exact match against EVM-format digital currency addresses published in the OFAC SDN list as of list_date; a non-match does not mean an address or its owner is not sanctioned or is safe. On-chain facts and labels come from public sources and can be incomplete." } } ``` ## More - Live health (JSON, refreshed every minute): https://www.zero.xyz/c/base-batch-address-screen-x402-aa5fc224/health.json - [Zero catalog index](https://www.zero.xyz/llms.txt) - [Other services from api.x402risk.com](https://www.zero.xyz/host/api.x402risk.com/llms.txt)