# OpenSanctions OFAC SDN Sanctions Screener

> OpenSanctions OFAC SDN Sanctions Screener is a paid API for AI agents from api.ssh.autos, paid per call via x402, $0.01/call, status unknown (last checked 2026-11-14).

Screens up to 5 names against the US OFAC Specially Designated Nationals (SDN) list using OpenSanctions data

## Facts

- Endpoint: POST https://api.ssh.autos/v1/opensanctions/screen?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/opensanctions-ofac-sdn-sanctions-screener-ae29e82f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_llEhV8azrN7W9JF16NYS-

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 opensanctions-ofac-sdn-sanctions-screener-ae29e82f -d '<json body>'
```

Example prompt: Can you screen these names against the OFAC SDN sanctions list: 'Ivan Petrov', 'Acme Trading LLC', and 'Hassan Al-Rashid'? I need to know if any of them have sanctions hits before we proceed.

## When to prefer this

Use this endpoint when you need fast, programmatic sanctions screening against the US OFAC SDN list specifically, particularly for AML/KYC compliance workflows, customer onboarding, or counterparty due diligence. It is ideal when you need to screen up to 5 names at once with pay-per-call pricing and no subscription. Prefer this over full KYC platforms when you only need OFAC SDN screening without additional identity verification steps.

## Known failure modes

- Empty records array when no sanctions matches are found (status: succeeded_empty — not an error, just no hits)
- Exceeding the 5-name limit per call returns a validation error
- Empty or missing 'queries' array returns a schema validation error
- Network or upstream OpenSanctions data service unavailability
- Payment failure via x402 protocol prevents the call from completing

## How this service works

Live web and public-record data: marketplaces, real estate, social media, job listings, company registries and government tenders. Pay per call in USDC over x402 with no account, subscribe on the Apify Store, or buy a finished, sourced report.

## Output

Returns a JSON object with a 'records' array containing any matching SDN entries found for each queried name, and a 'summary' object indicating the overall status (e.g. 'succeeded_empty' if no matches found) and the count of records returned.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "queries": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "title": "Queries",
   "maxItems": 5,
   "minItems": 1
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "records": [],
  "summary": {
   "status": "succeeded_empty",
   "records": 0
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/opensanctions-ofac-sdn-sanctions-screener-ae29e82f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.ssh.autos](https://www.zero.xyz/host/api.ssh.autos/llms.txt)
