US OFAC SDN · public

Sanctions screening API — OFAC SDN, live.

Screen any party against the US OFAC Specially Designated Nationals list — designations apply the instant OFAC posts them, so a model can't know recent ones.

The call

Keyless over MCP, or one REST call with a free key. Every datapoint is provenance-stamped and citeable.

# REST (free key)
curl -H "X-API-Key: $KEY" "https://dynamicfeed.ai/sanctions?name=Acme%20Corp"

# MCP (keyless) — point any client at https://dynamicfeed.ai/mcp, then call:
sanctions_screen(name="Acme Corp")

Sample response

{ "query": "Acme Corp", "results": [], "note": "no SDN match",
  "source": "US OFAC SDN", "observed_at": "2026-06-03T00:00:00Z" }

Why live data

OFAC designations are legally binding the moment they post and change constantly — exactly the post-cutoff data a compliance agent must check live, never from memory.

Use it for

Get a free API key See it live API docs

FAQ

Is this authoritative / legal advice?

No — it is informational. Always confirm the full entry on the official OFAC source before acting.

Source?

US Treasury OFAC SDN list, public.

Keyless?

MCP is keyless; REST uses a free key.

Related live feeds

CVE APIProvider uptime APIMCP serverAll use cases →