Add Verifex as an evidence layer.
You do not need to replace your sanctions screening provider to get reviewable evidence. Verifex runs beside it: as a secondary check, benchmark layer, regional KYB desk, and structured decision recorder.
How teams use Verifex alongside their provider.
Secondary Screening Layer
Run Verifex alongside your primary provider to catch edge cases, verify contested matches, and reduce false-positive fatigue without replacing your current workflow.
Second opinions arrive with the match reasoning, so contested alerts close faster.
See screening APIEvidence Capsule Generator
Your primary provider returns a score. Verifex preserves the full decision context: match rationale, list versions, algorithm version, and reviewer action, in a structured, exportable capsule.
Every screening decision becomes auditable with a single API call.
Explore Evidence CapsuleInternal Benchmark & Regression Layer
Run the same entity through both providers and compare. Verifex publishes its benchmark methodology, so you can design the same comparison on your own names.
Published benchmark methodology, with withdrawn results marked as withdrawn rather than quietly removed.
View benchmarkAudit Export Layer
When auditors ask 'What was checked and why?', export structured JSON evidence with point-in-time list versions, match explanations, and decision hashes.
JSON export available now. PDF planned for future release.
See compliance pageRegional KYB Support
Your primary provider may not cover Turkey or Azerbaijan company verification. Verifex KYB dossiers fill that gap with registry evidence, ownership mapping, and sanctions screening.
Turkey & Azerbaijan KYB dossiers: analyst-reviewed, with structured JSON delivery.
Explore KYBFallback API
If your primary provider experiences downtime or rate limits, Verifex can be evaluated as a secondary screening path. Consult current service status and your own resilience requirements before relying on it as a fallback.
Inspect served coverage and operational status in the workflow you intend to use.
Check statusFour steps. No migration.
Parallel or sequential
Call Verifex after your primary provider, or run both in parallel. No migration required.
Merge or compare
Use Verifex match rationale to adjudicate disagreements. Export both results for audit.
Preserve evidence
Record the response evidence state. Retrieve an Evidence Capsule only once it is reported as available.
Review quarterly
Compare provider drift using Verifex benchmark cases. Adjust thresholds based on real data.
Official SDKs
Node · Python · Go · Rust
Benchmark
97.33% exact-name recall (95% CI 94.83–98.64%), measured August 12, 2026 on Production Engine vNext, self-administered and not independent validation. The deployed engine has changed since that measurement, so this describes the configuration tested on that date rather than current behaviour; the latest served measurement (October 13, 2026) is on the benchmark page, with every gate.
Latency
Low-latency · result in the same API request
Free trial
5 screens, no card
Common questions.
Do I need to replace my current provider?
No. Verifex is designed to run alongside existing screening infrastructure. You can call it as a secondary check, a fallback, or an evidence layer without changing your primary workflow.
How does the Evidence Capsule work with another provider's results?
The capsule captures Verifex's own screening context. You can store both provider results in your case management system and reference Verifex capsules for match rationale, list versions, and adjudication reasoning.
Is there a cost for running Verifex as a secondary layer?
Start with a free trial of 5 screens on the Starter source set, no credit card. Starter (€49/mo) gives 2,500 screens with 30-day audit retention. You only pay for what you use. Starter, Growth and Pro are free for 7 days. The first payment is taken on day 8 — the monthly price, or the full year on annual billing. Cancel before then and you pay nothing.
Can I use Verifex for specific regions only?
Yes. Many teams use Verifex primarily for Turkey and Azerbaijan KYB, or as a PEP/adverse-media supplement where their primary provider has gaps.
What integration effort is required?
The REST API, OpenAPI contract, and supported SDKs are available for evaluation. Integration effort depends on the controls, coverage checks, and evidence handling required by your workflow.
Run Verifex beside your provider.
No migration. No minimum contract. Start with 5 free screens and see how the evidence layer improves your audit readiness.
- 5 free trial screens
- No credit card required
- Cancel anytime