Embedded / API partners
Add compliance screening to your own product.
Call Verifex server-side from your backend. One request returns a risk level, matches, and a request ID you can store as evidence — so your platform can offer sanctions, PEP, and watchlist screening without building a screening engine.
Free plan available · Dashboard and API · No sales call required to start.
Who it's for
Embedded SaaS platforms
Compliance, payments, lending, marketplace, or onboarding products that need to screen their own customers' counterparties.
Report and dossier products
Tools that generate KYC/AML reports and want source-backed screening results inside their output.
API partners and OEMs
Teams that resell or embed screening under a commercial agreement. Embedded and commercial use requires authorization.
What it does
- Runs server-to-server — your keys and your users' data never touch the browser.
- Returns risk level, matches, confidence, source context, and a request ID per call.
- Stores each screening as a retrievable evidence record you can reference in your product.
- Supports single and batch screening, plus webhooks for monitoring updates.
What it does not do
- Does not make compliance decisions for your users or certify counterparties.
- Does not grant resale or embedded rights by default — commercial use requires authorization.
- Does not guarantee regulatory outcomes or complete risk clearance.
Use the dashboard first. Integrate the API when ready.
Prototype a screening in the dashboard with no code, confirm the result shape, then move to the API.
Authenticate with an API key, POST a name and type, and read back risk level, matches, and a request ID. OpenAPI spec and SDKs for Python, Node.js, Go, and Rust.
curl -X POST https://api.verifex.dev/v1/screen \
-H "Authorization: Bearer vfx_your_api_key" \
-H "Content-Type: application/json" \
-d '{"name": "Example Trading Ltd", "type": "company"}'Each call your platform makes can include the original input, normalized query, source context, timestamp, matches, confidence, and a request ID — exportable as structured evidence your users can keep in their AML file.
See how Evidence Capsules workCounts reflect active production records. Most of the 4.8M is company/KYB data via GLEIF. We describe this as compliance/KYB records, not sanctions records.
Related
Frequently asked questions
Can I embed Verifex inside my own product?
Yes, server-side, under a commercial/embedded agreement. Standard plans cover internal use; embedding screening into a product you offer to your own customers requires authorization. Contact hello@verifex.dev to discuss.
Is data processed server-side?
Yes. Verifex is designed for server-to-server use. Your API key and the names you screen are sent from your backend, not the end user's browser.
Do my users see Verifex branding?
No. The API returns structured JSON. How you present results inside your product is up to you, subject to your agreement and attribution terms.
Does a clear result guarantee my user's counterparty is safe?
No. A clear result means no match was found in screened sources at screening time. Verifex provides screening infrastructure and data-derived results, not legal or compliance advice.
Run your first screening free
Verifex provides screening infrastructure and data-derived results, not legal or compliance advice. A clear result means no match was found in screened sources at screening time.