Six Use Cases
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.
Reduces false-positive overload by up to 40% in pilot data.
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 and test cases, so you can measure drift and accuracy over time.
Published 122-case benchmark with disclosed methodology.
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 with structured JSON delivery.
Explore KYBFallback API
If your primary provider experiences downtime or rate limits, Verifex serves as a hot standby with sub-300ms p99 latency and 99.9% uptime target.
p50 45ms, p99 276ms on published benchmark.
Check statusIntegration
Four 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
Every Verifex screening generates an Evidence Capsule with list versions, scores, and rationale.
Review quarterly
Compare provider drift using Verifex benchmark cases. Adjust thresholds based on real data.
Official SDKs
Node · Python · Go · Rust
Benchmark
122 cases, 96.6% F1
Latency
p50 45ms · p99 276ms
Free Tier
50 screens/month
FAQ
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 50 free screens/month on the Free plan. Starter ($49/mo) gives 2,000 screens with 30-day audit retention. You only pay for what you use.
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?
Minimal. Official SDKs are available for Node.js, Python, Go, and Rust. A single POST /v1/screen call takes minutes to integrate. No SAML, no mandatory onboarding calls.