# x402 OFAC SDN Screen API

> x402 OFAC SDN Screen 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-10).

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

## Facts

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

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-screen-api-5577316a -d '<json body>'
```

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

## When to prefer this

Choose this endpoint when you need a fast, pay-per-call OFAC SDN fuzzy screen without committing to a subscription-based compliance service. It is ideal for AI agents performing ad hoc sanctions checks on individual names during onboarding, due diligence, or transaction workflows. It is not a substitute for certified compliance clearance — use it as a directional signal to flag potential matches for human review.

## Known failure modes

- Name query returns zero hits even for known sanctioned entities if threshold is set too high — lower the threshold to improve recall
- Fuzzy matching may produce false positives for common names — review scores carefully before acting
- SDN list date ('list_as_of') may lag real-time OFAC updates — check currency before relying on results for high-stakes decisions
- Malformed or missing 'query' field returns a validation error
- Exceeding the max limit of 50 hits is silently capped or returns an error depending on implementation
- Payment failure via x402 prevents the call from completing

## 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 containing: a list of hits (each with a match score, entity name, and match type such as primary or alias), the original query, total hit count, the date the SDN list was last updated, and a disclaimer stating these 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-screen-api-5577316a/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)
