# x402 OFAC SDN Entity Number Lookup

> x402 OFAC SDN Entity Number Lookup is a paid API for AI agents from x402-ofac-api.vercel.app, paid per call via x402, $0.1/call, status unknown (last checked 2026-10-13).

Looks up an OFAC SDN entity by its numeric entity number and returns match details, with payment via USDC on Base per the x402 protocol.

## Facts

- Endpoint: POST https://x402-ofac-api.vercel.app/api/v1/entity?utm_source=zero.xyz
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-ofac-sdn-entity-number-lookup-470abccb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4pyfzeCD3eNN3_eMQ2oyv

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-entity-number-lookup-470abccb -d '<json body>'
```

Example prompt: Can you check the OFAC SDN list for entity number 306 and tell me what name comes back?

## When to prefer this

Use this endpoint when you already have a specific OFAC SDN entity number and need to retrieve the corresponding record directly — it is faster and more precise than fuzzy name screening. Prefer this over name-based screening when the entity number is known from a prior lookup or database. Best for agent workflows that need pay-per-call, audit-trail-friendly OFAC checks without a subscription.

## Known failure modes

- Entity number not found — returns found: false with no entity details
- Invalid or malformed ent_num input — may return validation error
- Payment failure via x402 protocol — call not executed if USDC payment not confirmed
- OFAC list data temporarily unavailable — service may return error
- Rate limiting or infrastructure issues on Vercel hosting

## 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 'found' boolean, the entity details (name and entity number) if matched, a disclaimer noting this is directional/not a clearance, and the timestamp of the SDN list version used.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "ent_num": {
   "type": "string",
   "description": "OFAC SDN entity number"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "found": true,
  "entity": {
   "name": "BANCO NACIONAL DE CUBA",
   "ent_num": "306"
  },
  "disclaimer": "Directional OFAC SDN lookup only...",
  "list_as_of": "2026-10-10T04:18:02.953473+00:00"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-ofac-sdn-entity-number-lookup-470abccb/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)