Jev vs KYC vendors
A KYC vendor (Jumio-class, government ID + liveness + sanctions) produces an attested identity decision. Jev can triage whether a text packet looks complete or inconsistent. It does not verify a passport.
Independent. Not legal advice. Not a KYC product. Official Jev: text state only. docs.typesafe.ai.
Comparison scope
Sanctions, PEP, and ID authenticity stay with licensed vendors and your compliance program. Jev might flag “this application narrative contradicts the stated country” for a human.
Criteria that decide the architecture
| Axis | Jev (System One) | KYC vendors |
|---|---|---|
| ID + liveness | No | Wins |
| Sanctions lists | No (unless you put hits in state) | Vendor / list providers |
| Narrative consistency | Noul/Choice | Sometimes rules |
| Regulatory attestation | None | Their SOC/report |
Decision quality and control
Mis-using Jev as “AI KYC” is how you fail an audit. Keep the vendor of record. Use Jev only on leftover language after structured checks.
Integration trade-offs
Vendor result + extracted fields → optional Jev questions → human KYC queue. Fail closed. Images never go to Jev.
TypeSafe’s public models page lists jev-1.13 at $0.042 per million input tokens with output tokens free — a vendor claim, not a jev.pro measurement. Confirm on the models page before you bid.
When each approach fits
Prefer Jev when
- Completeness / consistency on text after vendor checks
Prefer KYC vendors when
- You need identity proofing or list screening
Vendor attests identity; Jev labels residual text risk; compliance decides.
Residual narrative after the vendor attests
Identity proofing stays with a licensed vendor: government ID, liveness, and list screening. Jev sees text you already extracted, never a selfie. Sketch: vendor result + structured fields (country, name-as-entered) + the applicant’s free-text explanation → Noul “narrative contradicts stated country” and Choice complete / missing_source_of_funds / inconsistent_address / other → human KYC queue. Pin jev-1.13.0. Fail closed on timeout. Images never leave the vendor pipeline for TypeSafe.
TypeSafe’s $0.042 / M input figure is a vendor claim. Do not “save KYC fees” by sending passport pixels; the API will not accept them, and an auditor will not accept a Noul as attestation. Jaggedness: do not ask Jev to checksum an ID number.
How “AI KYC” fails an audit
- Jev as the vendor of record. A schema-safe Choice is not a passport check and is not a sanctions hit. Keep the SOC report where it belongs.
- Images or PDFs in the POST. Official models page: text state only. OCR first if you must, then the leftover language question.
- Sanctions “in the model.” Unless you put list hits in
state, Jev has no list. Do not invent one. - PII sprawl. Full ID numbers in
stateare a DPA problem, not a prompt problem. Minimize. This site is not your DPA. - Generation of a SAR narrative. Jev does not write filings. Your compliance tooling does.
When not to use Jev here
Do not use Jev for identity proofing, liveness, PEP/sanctions, or any attested “this person is who they say.” Use it only for completeness or consistency on leftover text after structured vendor checks. If you have no leftover language, you do not need this pairing.
What this page does not claim
-
Not a substitute for KYC/AML programs.
-
No pass-rate claims.
-
Schema-safe output is not the same as factual correctness.
-
No independent bake-off numbers live here.
FAQ
Can Jev check a selfie? No image input.
GDPR / PII in state?
Read TypeSafe Legal / DPA. Minimize fields. This site is not your DPA.
Is a high Noul “cleared for onboarding”? No. That is a human/vendor decision. Jev only labeled residual text.
Disclaimer
This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai. Never treat jev.pro as TypeSafe official documentation. We do not sell, issue, or proxy API keys.
Hub: Comparisons. Siblings: vs fraud scores, vs invoice ocr, questions for legal. Canonical: https://docs.typesafe.ai.