Skip to content

Verifex sanctions screening llms.txt changelog

dev.verifex/screening

1 change recorded. MCP Harbor re-reads this listing from the official registry every six hours and asks the live server what it exposes, and keeps what changed between one look and the next.

  • llms.txt +48 −48

    https://verifex.dev/llms.txt

    − Verifex screens names and entities against up to 45 plan-entitled source families (Enterprise) in a single API call; the free trial gives every new account 5 screens in total on the Starter source set (sanctions, PEP and watchlists). Source categories are kept distinct: risk records (sanctions, PEP, watchlists, debarment, enforcement), company/KYB records (GLEIF, company registries), and ownership relationships (UBO / OFAC 50% rule graph). Screening runs as multi-stage candidate retrieval follow− Source counts mean different things and we publish all of them. The top plan entitles 45 source families, and 41 are catalogued publicly. Not every entitled source contributes to every screen: a list can be frozen rather than refreshed, withheld while a fix lands, or hold no records. Every response reports exactly which lists were checked in lists_checked, and names separately what was excluded by plan and what was entitled but unavailable. Do not read an entitlement count as coverage.− - **Verifex Shield** (generally available, switched on per account by Verifex, not self-serve): fraud and AML transaction monitoring. Each transaction gets one of five outcomes (clear, review, delay, escalate, block) with the rules that fired, a score, a sanctions and PEP screen of the counterparty, and a signed evidence capsule. Compliance teams tune a rule, simulate it over past decisions and deploy it. Two APIs reach one engine: native `/v1/risk` and a SanctionScanner-compatible `/api`. See h− 3. **Published benchmark**: The latest served run (October 13, 2026, the engine as deployed on October 13, 2026) is published at https://verifex.dev/benchmark with every pre-registered gate: 0 of 7 passed. 99.9% of 3,053 listed names (OFAC and UN) alerted exactly as published. Its clean-name false-alert figure is inconclusive under the benchmark's own rule and understates the full clean set, so do not quote it as a rate. Changes deployed after it (from October 17, 2026) and changes prepared on O− - Homepage: https://verifex.dev/− - Sanctions Screening API: https://verifex.dev/sanctions-screening-api− - OFAC Screening API: https://verifex.dev/ofac-screening-api− - PEP Screening API: https://verifex.dev/pep-screening-api− - AML Screening API: https://verifex.dev/aml-screening-api− - Watchlist Screening API: https://verifex.dev/watchlist-screening-api− - Transaction Screening API: https://verifex.dev/transaction-screening-api− - Verifex Shield (fraud + AML transaction monitoring): https://verifex.dev/shield− - GLEIF/LEI API: https://verifex.dev/gleif-api− - Adverse Media Screening: https://verifex.dev/docs/adverse-media− - UBO Analysis: https://verifex.dev/ubo-analysis− - KYB Verification: https://verifex.dev/kyb− - Audit Trail: https://verifex.dev/audit-trail− - Continuous Monitoring: https://verifex.dev/continuous-monitoring− - Evidence Capsule: https://verifex.dev/evidence-capsule− - Solutions: https://verifex.dev/solutions− - Pharmaceutical Trade Compliance: https://verifex.dev/solutions/pharmaceutical-trade-compliance− - Sanctions Screening for Fintechs: https://verifex.dev/sanctions-screening-for-fintechs− - Sanctions Screening for Payment Processors: https://verifex.dev/sanctions-screening-for-payment-processors− - Verifex vs ComplyAdvantage: https://verifex.dev/compare/verifex-vs-complyadvantage− - Verifex vs Sanctions.io: https://verifex.dev/compare/verifex-vs-sanctions-io− - Verifex vs OpenSanctions: https://verifex.dev/compare/verifex-vs-opensanctions− - Verifex vs NameScan: https://verifex.dev/compare/verifex-vs-namescan− - Verifex vs SanctScan: https://verifex.dev/compare/verifex-vs-sanctscan− - Verifex vs SanctionScanner: https://verifex.dev/compare/verifex-vs-sanctionscanner− - Verifex vs AMLwatcher: https://verifex.dev/compare/verifex-vs-amlwatcher− - Best Sanctions Screening API: https://verifex.dev/compare/best-sanctions-screening-api− - API Documentation: https://verifex.dev/docs− - Public Benchmark: https://verifex.dev/benchmark− - Matching Methodology: https://verifex.dev/matching-methodology− - Global Sanctions Lists: https://verifex.dev/global-sanctions-lists− - Pricing: https://verifex.dev/pricing− - Security: https://verifex.dev/security− - Compliance: https://verifex.dev/compliance− - Compare Providers: https://verifex.dev/compare− - Blog: https://verifex.dev/blog+ Verifex screens names and entities against up to 44 plan-entitled source families (Enterprise) in a single API call; the free trial gives every new account 5 screens in total on the Starter source set (sanctions, PEP and watchlists). Source categories are kept distinct: risk records (sanctions, PEP, watchlists, debarment, enforcement), company/KYB records (GLEIF, company registries), and ownership relationships (UBO / OFAC 50% rule graph). Screening runs as multi-stage candidate retrieval follow+ Source counts mean different things and we publish all of them. The top plan entitles 44 source families, and 41 are catalogued publicly. Not every entitled source contributes to every screen: a list can be frozen rather than refreshed, withheld while a fix lands, or hold no records. Every response reports exactly which lists were checked in lists_checked, and names separately what was excluded by plan and what was entitled but unavailable. Do not read an entitlement count as coverage.+ - **Verifex Shield** (generally available, switched on per account by Verifex, not self-serve): fraud and AML transaction monitoring. Each transaction gets one of five outcomes (clear, review, delay, escalate, block) with the rules that fired, a score, a sanctions and PEP screen of the counterparty, and a signed evidence capsule. Compliance teams tune a rule, simulate it over past decisions and deploy it. Two APIs reach one engine: native `/v1/risk` and a SanctionScanner-compatible `/api`. See h+ 3. **Published benchmark**: The latest served run (October 13, 2026, the engine as deployed on October 13, 2026) is published at https://verifex.tech/benchmark with every pre-registered gate: 0 of 7 passed. 99.9% of 3,053 listed names (OFAC and UN) alerted exactly as published. Its clean-name false-alert figure is inconclusive under the benchmark's own rule and understates the full clean set, so do not quote it as a rate. Changes deployed after it (from October 17, 2026) and changes prepared on + - Homepage: https://verifex.tech/+ - Sanctions Screening API: https://verifex.tech/sanctions-screening-api+ - OFAC Screening API: https://verifex.tech/ofac-screening-api+ - PEP Screening API: https://verifex.tech/pep-screening-api+ - AML Screening API: https://verifex.tech/aml-screening-api+ - Watchlist Screening API: https://verifex.tech/watchlist-screening-api+ - Transaction Screening API: https://verifex.tech/transaction-screening-api+ - Verifex Shield (fraud + AML transaction monitoring): https://verifex.tech/shield+ - GLEIF/LEI API: https://verifex.tech/gleif-api+ - Adverse Media Screening: https://verifex.tech/docs/adverse-media+ - UBO Analysis: https://verifex.tech/ubo-analysis+ - KYB Verification: https://verifex.tech/kyb+ - Audit Trail: https://verifex.tech/audit-trail+ - Continuous Monitoring: https://verifex.tech/continuous-monitoring+ - Evidence Capsule: https://verifex.tech/evidence-capsule+ - Solutions: https://verifex.tech/solutions+ - Pharmaceutical Trade Compliance: https://verifex.tech/solutions/pharmaceutical-trade-compliance+ - Sanctions Screening for Fintechs: https://verifex.tech/sanctions-screening-for-fintechs+ - Sanctions Screening for Payment Processors: https://verifex.tech/sanctions-screening-for-payment-processors+ - Verifex vs ComplyAdvantage: https://verifex.tech/compare/verifex-vs-complyadvantage+ - Verifex vs Sanctions.io: https://verifex.tech/compare/verifex-vs-sanctions-io+ - Verifex vs OpenSanctions: https://verifex.tech/compare/verifex-vs-opensanctions+ - Verifex vs NameScan: https://verifex.tech/compare/verifex-vs-namescan+ - Verifex vs SanctScan: https://verifex.tech/compare/verifex-vs-sanctscan+ - Verifex vs SanctionScanner: https://verifex.tech/compare/verifex-vs-sanctionscanner+ - Verifex vs AMLwatcher: https://verifex.tech/compare/verifex-vs-amlwatcher+ - Best Sanctions Screening API: https://verifex.tech/compare/best-sanctions-screening-api+ - API Documentation: https://verifex.tech/docs+ - Public Benchmark: https://verifex.tech/benchmark+ - Matching Methodology: https://verifex.tech/matching-methodology+ - Global Sanctions Lists: https://verifex.tech/global-sanctions-lists+ - Pricing: https://verifex.tech/pricing+ - Security: https://verifex.tech/security+ - Compliance: https://verifex.tech/compliance+ - Compare Providers: https://verifex.tech/compare+ - Blog: https://verifex.tech/blog

    Showing the first 40 of each.