Sanctions Screening
Providers using this tag (25)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Strong 3 Solid coverage with minor gaps
Developing 9 Usable, with meaningful gaps to close
Thin 5 Limited public surface area
Minimal 5 Almost no public developer surface
APIs with this tag (10)
Ranked by the provider's API Evangelist rating — the Kin Score is scored per provider, not per API, so every API of a provider shares its band. How the rating works →
Developing 6 Usable, with meaningful gaps to close
Thin 1 Limited public surface area
Emerging 2 Early or largely undocumented
Minimal 1 Almost no public developer surface
Companies reaching this through an API (6)
These companies publish an API, specification or operation carrying “Sanctions Screening” but do not classify their business under it. Listed unranked and kept out of the count above, because one tagged operation is not a statement about what a company does.
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 25 providers in the APIs.io catalog tagged Sanctions Screening, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Developer Ergonomics | 38 | 23.8 | +14.2 | 25 |
| Access Clarity | 39.6 | 27.2 | +12.4 | 25 |
| Contract Quality | 32.4 | 20.4 | +12 | 25 |
| Operational Transparency | 25.8 | 14.4 | +11.4 | 25 |
| Discoverability | 68.7 | 61.4 | +7.3 | 25 |
| Contract Governance | 9.9 | 6.6 | +3.3 | 25 |
A facet is averaged over the members that carry it, not over the whole cohort — the “Scored” column is that count. Averaging an absent facet as zero would score our own coverage gaps as the providers’ posture.
| Artifact | This cohort | Catalog | Difference |
|---|---|---|---|
| MCP server (any) | 28% | 11% | +17 |
| MCP server (first-party) | 32% | 13% | +19 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 16% | 12% | +4 |
| Security | 96% | 96% | 0 |
| Arazzo workflows | 4% | 2% | +2 |
| Governance rules | 4% | 13% | -9 |
mcp_pct counts any mcp/ artifact including ones API Evangelist derived from the provider OpenAPI; mcp_first_party_pct counts only servers the provider publishes. Prefer the latter.
- 1 OpenSanctions 73.1
- 2 iDenfy 64.8
- 3 ComplyAdvantage 63.4
- 4 ZenLedger 55
- 5 CipherOwl 53.6
- 6 Dotfile 51.4
- 7 Enigma Analytics 47.6
- 8 Sigma360 45.8
- 9 Parcha 45.2
- 10 sanctions.io 43.3
- 1 ComplyAdvantage 47.3
- 2 iDenfy 41.5
- 3 Salv 41.5
- 4 Enigma Analytics 36.3
- 5 Aclid 35.1
- 6 ARAKEL Machine Evidence Network 33.9
- 7 Dotfile 33.3
- 8 ZenLedger 31.1
- 9 OpenSanctions 29.9
- 10 ThetaRay 27.3
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.