Frequently asked questions

180 sanctions regimes — OFAC, the UN Security Council, the EU Council, UK HMT, SECO and national authorities — plus 1,000+ watchlists spanning regulatory enforcement, law enforcement, debarment and probity lists across 190+ jurisdictions. The complete itemised list of 1,197 source feeds, with live record counts, is available on request.

Yes, in early access: 3,000+ PEP sources with position-level records — office held, country, start and end dates — filterable by class (1, 1-SOE, 2, 3, 4) and by sitting or former status. Coverage spans heads of state, legislators, military officials, SOE executives and their relatives and close associates, and expands continuously.

Persons, organisations, vessels and aircraft. Where the issuing list publishes an identifier — an IMO number for a vessel, a registration number for a company, a passport for a person — it is stored and matchable exactly.

Not today, and we will not claim otherwise. The index covers sanctions, watchlist, enforcement, probity and PEP data. When new categories reach production quality they will be announced when they reach production quality.

Sources are monitored continuously and new designations reach the index in near real time — not on a nightly batch.

Retrieval combines edit-distance fuzziness, phonetic encoding and n-gram matching over names and aliases. AI entity resolution clusters transliterations and aliases across 50+ languages into unified entities, so a hit on "Володимир Путін" and "Vladimir Putin" resolves to the same record.

Date-of-birth, nationality and country filters are discriminators, not gates. A sanctions record that carries no DOB still passes a DOB filter — only a genuine mismatch excludes it. Sanctions lists frequently omit these fields, and hard-filtering on them silently drops designated parties. Strict exclusion is available as an explicit opt-in for workflows that require it.

Scores are relevance rankings for ordering results within a query. They are honest about what they are: not calibrated probabilities, and not comparable across different queries. We recommend review workflows built on ranked results plus the structured evidence on each record, and we say so rather than selling a magic number.

A REST API with JSON responses — first call in about five minutes via the quickstart. Batch screening accepts up to 500 queries per request. Bulk flat files (JSON or CSV snapshots of the full database) are available for on-premise matching engines.

Typical screening responses return in well under 150 ms including query execution; the index-side query itself usually completes in under 30 ms.

Every record carries its source attributions, and every entity merge made by the resolution layer carries a human-readable rationale. Your reviewers can trace any match from the API response back to the issuing authority.

Yes. The web sandbox is free with no signup, and API keys include 25 free searches with no card required.

By monthly search volume, with flat-file delivery on Scale and Enterprise plans. No setup fees and no hidden costs — see pricing.