# x402 OFAC SDN Sanctions Screening API

> x402 OFAC SDN Sanctions Screening API 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-12).

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

## Facts

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

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-screening-api-849511cf -d '<json body>'
```

Example prompt: Can you screen 'Banco Nacional de Cuba' against the OFAC SDN list and return up to 10 matches using a match threshold of 0.6?

## When to prefer this

Use this endpoint when you need a fast, pay-per-call, programmatic OFAC SDN screen for a single name or alias without committing to a subscription compliance service. It is ideal for AI agents doing ad-hoc due diligence, pre-transaction checks, or low-volume KYC screening where you want fuzzy matching with a configurable threshold. Not appropriate as a definitive legal clearance — results must be reviewed by a compliance officer for regulatory purposes.

## Known failure modes

- Query string is empty or missing — API returns a 400 or empty result
- Threshold set too high (close to 1.0) — returns zero hits even for exact matches due to scoring nuance
- Threshold set too low (near 0) — returns an overwhelming number of false positives
- Payment not processed or insufficient USDC balance — 402 Payment Required response blocks the call
- SDN list may lag by hours relative to OFAC's live publication — stale list_as_of timestamp
- Max limit of 50 hits hard-capped — queries with many matches may silently truncate results

## 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 a list of potential SDN hits, each including the matched entity name, a similarity score (0–1), and the match method (e.g. primary name or alias). Also includes the total hit count, the query string, the SDN list timestamp, and a disclaimer that results are directional potential matches only — not a 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-screening-api-849511cf/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)