Sub-second screening across 1.5M+ sanctioned, PEP and enforcement records — including 265k politically-exposed persons across 205 jurisdictions — every decision sealed into WORM cryptographic evidence with RFC 6962 audit proofs. Screen against a non-overridable sanctions floor, then show an examiner exactly what was checked, when, and why.
Screening you can defend is not one model — it is layered controls that each fail closed. Every one of them is enforced server-side and written to the evidence chain.
Hard-sanctions matches surface at the platform floor regardless of any sensitivity slider. No UI control, key, or role can lower it — the floor is enforced in the engine, not the interface.
Each result is re-derived by an independent scorer and reconciled across three passes. Disagreements are flagged, never silently dropped.
Releasing or dismissing an asset-freeze match requires a distinct second approver. You cannot approve your own disposition — the platform refuses it.
Every screening seals the full candidate set, scores and list snapshot into a capsule, hash-chained to the last and archived to WORM storage.
Billing is counted from the same immutable decision log you are audited against. Start free with 200 screens a day; beyond that, subscribe to a plan or pay $1.50 per screening — no contract required either way.
A rate-limited, WAF-fronted REST API with scoped ssk_ keys, signed webhooks and per-tenant isolation. Test and live keys never mix.
A single REST endpoint returns a decision, the scored candidate set with a factor breakdown, and the id of the sealed evidence capsule.
ssk_test_ and ssk_live_ keys from the console, each limited to the scopes it needs.audit_id resolves to a WORM-sealed capsule with the full decision fingerprint.curl -X POST https://api.celmus.com/v1/screen/entity \
-H "Authorization: Bearer ssk_live_…" \
-H "Content-Type: application/json" \
-d '{
"subject": {
"entity_type": "individual",
"name": "Alexander Volkov",
"dob": "1984-03-12",
"nationalities": ["CY"]
}
}'
# → {
# "decision": "review",
# "matches": [{ "canonical_name": "…",
# "score_adjusted": 94, "restriction": "…" }],
# "audit_id": "a7f3c9e2-…",
# "capsule": { "state": "sealed" } }Sanctions exposure is not only a banking problem. If a regulator, an auditor or a counterparty can ask who did you screen, against what, and when, celmus is built to answer it. The obligation stays yours — celmus is the infrastructure and the evidence behind the answer.
Screen sender and beneficiary on every transfer, at any amount, before funds move. Transaction screening with both parties, corridor context and a decision record per attempt — for FINTRAC, FinCEN and equivalent regimes.
Customer due diligence at onboarding and re-screening thereafter, with structured PEP occupancy and relatives/close-associate links so enhanced due diligence is evidenced rather than assumed.
One REST call per entity, or batch your whole book. Sandbox keys in minutes, the same corpus as production, and per-tenant isolation if you screen on behalf of your own customers.
Sanctioned wallet addresses are carried as first-class entities alongside people and companies, so a VASP can screen a counterparty and a destination address through the same control.
Debarment and exclusion coverage — including US federal exclusions and multilateral development-bank ineligibility — so supplier onboarding catches barred vendors, not only sanctioned ones.
Law, accountancy, real estate, gaming and platforms that onboard sellers: the same screening and the same examiner-ready evidence, without building a compliance stack to get it.
Vessels and aircraft are covered too, for trade finance and shipping exposure. Not sure whether your obligation fits? Start free — 200 screens a day, no card — or ask sales@celmus.com.
Start free with 200 screens per day — no card. Past that it is $1.50 per screening, or a plan below with an included monthly allowance at a much lower effective rate. Allowances reset each month and do not roll over. Every tier includes sanctions, PEP, enforcement and adverse-media.
Every decision celmus makes is sealed, hash-chained and independently verifiable — so when an examiner asks what you checked, the answer is already written down.