# OFAC SDN Entity Lookup by UID

> OFAC SDN Entity Lookup by UID is a paid API for AI agents from data.japanagent.dev, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-13).

Fetches full OFAC Specially Designated Nationals (SDN) entity details by UID, including primary name, aliases, entity type, sanction programs, and remarks.

## Facts

- Endpoint: GET https://data.japanagent.dev/sanctions/entity/ofac/:uid
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ofac-sdn-entity-lookup-by-uid-5273bb64
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gze4HEvS5MmvkowfAt5-s

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 ofac-sdn-entity-lookup-by-uid-5273bb64
```

Example prompt: Pull up the full OFAC SDN record for entity UID 36 — I need the primary name, all known aliases, entity type, which sanction programs it's listed under, and any remarks.

## When to prefer this

Use this endpoint when you have a specific OFAC SDN UID and need the complete, structured entity record including all aliases and program details. Prefer this over a name-search endpoint when you already know the exact UID and need authoritative, deduplicated entity data for compliance or KYC workflows.

## Known failure modes

- UID not found — no SDN entity exists for the given number (404)
- Invalid UID format — non-numeric or malformed UID (400)
- OFAC data source temporarily unavailable (503)
- Payment required or payment verification failure (402)

## How this service works

Fetch full OFAC SDN entity details by UID: primary name, all known aliases, entity type, sanction programs, remarks.

## Output

Returns the full OFAC SDN entity record for the given UID, including the primary legal name, all known aliases, entity type (individual, organization, vessel, etc.), associated sanction programs, and any official OFAC remarks.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object",
     "required": [
      "uid"
     ],
     "properties": {
      "uid": {
       "type": "string",
       "description": "OFAC SDN entity number"
      }
     }
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ofac-sdn-entity-lookup-by-uid-5273bb64/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from data.japanagent.dev](https://www.zero.xyz/host/data.japanagent.dev/llms.txt)