← Compliance

Sanctions Screening

Screens a name against six official sanctions lists — US OFAC, UN, EU, UK OFSI, Switzerland SECO and Canada — with transliteration-aware fuzzy matching.

POST /v1/sanctions/screen · 5 credits

No account needed to try any endpoint on this page.
Deterministic endpoints answer from cache in single-digit milliseconds.
Every response carries a receipt: credits charged, cache status, duration.

Free try on this page → when you need a key, Proceed to pay · API access.

Try free Proceed to pay · API access Read the spec

POST/v1/sanctions/screen

Request

{
  "name": "Saddam Hussein"
}

no request sent yet

Response

Press Run to try free — no key needed.

1endpoints

—data points banked

—time series

—median response

Why this exists

Built for hostile input

A Turkish address arrives as "Cd." or "Cad." or "Caddesi", with the flat number glued to the building number. Generic parsers drop half of it silently. This one tells you what it could not place.

Every number carries its provenance

Each archived point stores the source URL and a content hash of the page it came from, and the archive is committed to a Merkle root anchored in Bitcoin. Every commitment — with its cutoff, leaf count and anchors — is published at /proof, so you can check for yourself how current the latest one is. The bulletins themselves are public and anyone can read them; what this adds is that a number you quote can be shown to be the number we held on that date, and that it has not been edited since.

You only pay for work

Repeated inputs come from cache and cost zero credits. If a response ever fails its own schema, the call is refunded automatically.

Endpointsexpand any row to see the parameters and call it live

Compliance1

/v1/sanctions/screen Sanctions Screening 5 credits

Screens a name against six official sanctions lists — US OFAC, UN, EU, UK OFSI, Switzerland SECO and Canada — with transliteration-aware fuzzy matching.

Six official lists are reduced to one schema, so a name is checked everywhere at once instead of six integrations. Cyrillic and Arabic names are transliterated, titles and corporate suffixes are stripped, and known spelling families are unified — "Abd al-Rahman", "Abdul Rahman" and "Abdulrahman" reach the same record. Every hit explains itself: which name matched, whether it was an alias the source flags as weak, and how the birth year and country compared. Supply `birthYear` whenever you have it; it removes most false positives. `asOf` screens against the lists as they stood on a past date, which is the question auditors actually ask — note that this is bounded by when our archive begins, reported in `coverage`.

Parameters

name*	string	Name to screen — person or organisation.
type	"any" \| "individual" \| "entity" \| "vessel" \| "aircraft"	Restrict to one subject type. Narrowing this removes most false positives. default "any"
birthYear	integer	Known birth year. The single strongest false-positive filter available.
country	string	Known country or nationality.
sources	"OFAC_SDN" \| "UN" \| "EU"[]	Defaults to all lists.
minScore	number	Score floor. 0.92+ reads as a match, 0.80+ as possible. default 0.75
limit	integer	default 10
asOf	string	Screen against the lists as they stood on this date. Limited by when our archive begins.

POST/v1/sanctions/screen

Request

{
  "name": "Saddam Hussein"
}

no request sent yet

Response

Press Run to try free — no key needed.

Pricingone key covers every endpoint

Free try on this page → when you need a key, Proceed to pay · API access.

Proceed to pay · API access All plans →

Credits are consumed per call and cache hits are free. Requests without a key run on a narrow per-IP demo quota so you can evaluate before signing up.

The API key is e-mailed the moment payment clears. Upgrades keep the same key, so your integration is never broken.

Want to finish the integration before paying?

Use it from an AI assistantthe same catalogue, exposed as MCP tools

Every endpoint is also published over the Model Context Protocol, so Claude, ChatGPT or your own agent can call it directly — no glue code, no wrapper functions. The assistant sees the same input schemas and the same metering.

Currently 68 tools. New endpoints appear automatically; nothing to update on your side.

claude_desktop_config.json

{
  "mcpServers": {
    "temsor": {
      "url": "https://api.temsor.com/mcp",
      "headers": { "x-api-key": "fk_live_…" }
    }
  }
}

Quickstart

Official client: npm install temsor-api · npmjs.com/package/temsor-api

Node.js

import Client from "temsor-api";

const api = new Client({ apiKey: KEY });
const r = await api.${(() => {
  const first = apis[0];
  return first.slug.split(/[/-]/).map((p, i) => (i === 0 ? p : p[0].toUpperCase() + p.slice(1))).join('');
})()}(${esc(JSON.stringify(apis[0].examples[0]?.input ?? {}))});
console.log(r, r.$meta);

cURL

curl -s https://api.temsor.com/v1/sanctions/screen \
  -H "content-type: application/json" \
  -H "x-api-key: fk_live_…" \
  -d '{"name":"Saddam Hussein"}'

JavaScript

const res = await fetch("https://api.temsor.com/v1/sanctions/screen", {
  method: "POST",
  headers: { "content-type": "application/json", "x-api-key": KEY },
  body: JSON.stringify({"name":"Saddam Hussein"})
});
const { data } = await res.json();

Python

import httpx
r = httpx.post("https://api.temsor.com/v1/sanctions/screen",
    headers={"x-api-key": KEY},
    json={"name":"Saddam Hussein"})
data = r.json()["data"]