# x402 Paid MCP — OFAC SDN Screening

> x402 Paid MCP — OFAC SDN Screening is a paid API for AI agents from x402-paid-mcp.vercel.app, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-13).

Searches the OFAC Specially Designated Nationals (SDN) list for sanctions matches against a given name, entity, or identifier, returning fuzzy-matched results scored by similarity threshold.

## Facts

- Endpoint: POST https://x402-paid-mcp.vercel.app/api/v1/ofac-sdn?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-paid-mcp-ofac-sdn-screening-ad821bd3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xz_RCpDwidZQbmr6vGAhT

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-paid-mcp-ofac-sdn-screening-ad821bd3 -d '<json body>'
```

Example prompt: Can you check if 'Viktor Bout' is on the OFAC SDN sanctions list, with a match threshold of 0.85 and return up to 5 results?

## When to prefer this

Prefer this endpoint when you need live, pay-per-call OFAC SDN screening without standing up your own compliance infrastructure, especially in crypto-native or Web3 workflows where USDC micropayments via x402 are natural. It is well-suited for agent-driven AML/KYC flows, transaction screening pipelines, or onboarding checks where you want fuzzy matching with a configurable threshold rather than exact-match only.

## Known failure modes

- Query string missing or empty — returns validation error
- Threshold out of valid range — may return error or unfiltered results
- Payment not completed (x402 protocol) — returns 402 Payment Required
- OFAC SDN data source temporarily unavailable — returns upstream error
- No matches found above threshold — returns empty results list

## How this service works

Paid MCP wrapping live x402 OFAC SDN and SHA-256 meters. USDC on Base (preferred) and Solana.

## Output

Returns a list of SDN matches for the queried name or entity, each with a similarity/confidence score, the matched name on the SDN list, and associated sanctions metadata such as entity type, program, and identifiers — capped by the specified limit and filtered by the specified threshold.

## 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,
  "potential_matches_only": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-paid-mcp-ofac-sdn-screening-ad821bd3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-paid-mcp.vercel.app](https://www.zero.xyz/host/x402-paid-mcp.vercel.app/llms.txt)