# x402 OFAC SDN Priority Screen API

> x402 OFAC SDN Priority Screen API is a paid API for AI agents from x402-ofac-api.vercel.app, paid per call via x402, $1/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 or Solana.

## Facts

- Endpoint: POST https://x402-ofac-api.vercel.app/api/v1/ofac-sdn-priority?utm_source=zero.xyz
- Price: $1/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-priority-screen-api-09080e17
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_osyC74EJhMW95JMaeeTo6

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-priority-screen-api-09080e17 -d '<json body>'
```

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

## When to prefer this

Choose this endpoint when you need a fast, pay-per-call OFAC SDN name screen without standing up your own sanctions data infrastructure. It is ideal for AI agents operating in financial, legal, or compliance workflows that need to flag potential sanctions exposure on an ad-hoc basis. Prefer this over self-hosted solutions when you want zero maintenance overhead and crypto-native micropayment billing via x402. Not suitable as a definitive compliance clearance — use it as a first-pass triage tool that surfaces candidates for human review.

## Known failure modes

- Missing or empty 'query' field returns an error — the name to screen is required
- Threshold values outside 0–1 range may cause validation errors
- Max limit capped at 50; requests for more will be clipped or rejected
- Payment failure via x402 (insufficient USDC balance or unsupported chain) results in 402 response before screening occurs
- Stale SDN list data if the upstream OFAC list has not been refreshed recently (check 'list_as_of' field)
- False positives are inherent to fuzzy matching — results are potential matches, not confirmed sanctions hits

## 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 SDN hits, each with a fuzzy match score (0–1), the matched entity name, and how the match was made (e.g. primary name or alias). Also includes total hit count, the original query, the SDN list's as-of timestamp, and a disclaimer clarifying this is directional screening only — not a compliance 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-priority-screen-api-09080e17/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)