# x402 OFAC SDN Sanctions Screen

> x402 OFAC SDN Sanctions Screen is a paid API for AI agents from x402-ofac-api.vercel.app, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-13).

Fuzzy-screens a person or organization name against the OFAC Specially Designated Nationals (SDN) list and returns potential matches with confidence scores, paid per-call in USDC via x402.

## Facts

- Endpoint: POST https://x402-ofac-api.vercel.app/sanctions-screen?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-ofac-sdn-sanctions-screen-9385711f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pDEIwsTVZnoEDhn5LWwvx

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 x402-ofac-sdn-sanctions-screen-9385711f -d '<json body>'
```

Example prompt: Screen 'Petrov Trading Group' against the OFAC SDN sanctions list and return up to 10 potential matches using a match threshold of 0.6 — flag anything that looks like a hit.

## When to prefer this

Choose this endpoint when an AI agent needs a fast, pay-per-call OFAC SDN screen without a subscription — ideal for low-volume compliance checks, agentic workflows requiring inline sanctions validation, or prototyping KYC/AML pipelines. The x402 micropayment model (USDC on Base) makes it cost-effective for sporadic use compared to enterprise sanctions APIs with monthly fees. Note: results are directional potential matches only and must not be used as a standalone compliance determination.

## Known failure modes

- Empty query string returns error or zero hits
- Threshold set too high (close to 1.0) may produce zero results even for true positives
- Threshold set too low produces excessive false positives
- SDN list date may lag real-world updates by hours or days
- Payment failure via x402 (insufficient USDC balance) blocks the call
- Name transliterations or spelling variants may not fuzzy-match correctly

## How this service works

Pay-per-call directional OFAC SDN screen for AI agents (USDC on Base + Solana via x402). Potential matches only — not clearance.

## Output

Returns a JSON object with an array of hits (each containing a match score, matched entity name, and match type such as 'primary' or 'alias'), total hit count, the query string used, the date the SDN list was last updated, and a disclaimer confirming results are directional potential matches only — not legal clearance.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "limit": {
   "type": "integer",
   "description": "Max hits to return (default 25, max 50)"
  },
  "query": {
   "type": "string",
   "description": "Name or alias to screen"
  },
  "threshold": {
   "type": "number",
   "description": "Match threshold 0-1 (default 0.55)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "hits": [
   {
    "score": 1,
    "entity": {
     "name": "BANCO NACIONAL DE CUBA"
    },
    "match_via": "primary"
   }
  ],
  "query": "BANCO NACIONAL DE CUBA",
  "hit_count": 1,
  "disclaimer": "Directional OFAC SDN screen only...",
  "list_as_of": "2026-10-10T04:18:02.953473+00:00",
  "potential_matches_only": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-ofac-sdn-sanctions-screen-9385711f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-ofac-api.vercel.app](https://www.zero.xyz/host/x402-ofac-api.vercel.app/llms.txt)