KYC evaluation with Jev
Jumio-class vendors, sanctions lists, and liveness stay the system of record. Jev can ask whether the leftover narrative looks complete or internally inconsistent. It does not verify a passport and it is not a licensed KYC program.
This unofficial page is the evaluation slice of the KYC residual-text decisions pack. Intent: apply the Jev (TypeSafe System One) decision model to KYC residual-text decisions evaluation. Primary search language: KYC Jev evaluation. Confirm patterns on docs.typesafe.ai. This site does not sell, issue, or proxy TypeSafe keys. Use a credential you already have from the console or a documented gateway.
Independent angle (cover ≠ clone): Vendor attests identity; Jev only labels residual application text after structured checks. Fail closed — not a clone of KYC-vendor IA or an “AI KYC” product page.
KYC use-case context
Evaluation for KYC residual-text decisions is a frozen harness, not a vibe check and not an opinion-blog “Jev review.” Labels: hold / proceed / escalate gold from KYC analysts, plus contradiction gold. We publish no unofficial accuracy.
Hub: Use cases. Compare, when the other tool is the real job: KYC vendors.
Evaluation inputs
Replay the same contract you ship:
{
"application": { "id": "APP-19", "narrative": "I live in Lisbon but the business is registered in Delaware for tax reasons." },
"vendor": { "id_result": "pass", "sanctions_hit": false, "country_claimed": "PT" },
"policy": { "consistency": "Flag country or occupancy claims that contradict vendor country_claimed." }
}Freeze questions, criteria, and jev-1.13.0. Record the response model.
Decision signals and actions
Score these, not a blog-grade star rating:
- False-proceed on planted contradictory narratives (must stay below your SLA)
- Analyst override rate
- Calls skipped because vendor already failed — those are successes of the fail-closed path
Pair auto-act errors with handoff rate. If the KYC queue router never acts, you have not evaluated KYC residual-text decisions — you have evaluated a human queue.
Do not treat a Noul of 0.5 as a “medium” KYC residual-text decisions score — it means yes and no are equally likely. Conjunctions stay in your code.
Guardrails and escalation
Promote a threshold only when the harness says auto-act error ≤ SLA and reviewers still catch the residual. TypeSafe’s confidence-gated examples use a lower bar for recoverable reads than for irreversible actions. Those numbers are illustrations. For KYC residual-text decisions, treat auto_approve_account as the high bar (opening an account or attesting identity). Tune on labels — see offline evaluation.
Evaluation and rollout notes
After any criteria edit, rerun before production. Cookbook lifts you see on TypeSafe pages are vendor claims — re-measure on your application narrative + vendor result summarys. Pin jev-1.13.0 (the versioned id) after you fit thresholds. jev-latest and the marketing line jev-1.13 can move. Log the response model. TypeSafe’s published list price for jev-1.13 is $0.042 per million input tokens (vendor claim — confirm on the models page); output tokens are free on that same page. Unused distractors still bill as input.
Official Python and JavaScript SDKs read TYPESAFE_API_KEY and retry documented 429/529. This site does not sell, issue, or proxy TypeSafe keys. Use a credential you already have from the console or a documented gateway.
Pack map
| Slice | Page |
|---|---|
| Graph and primitives | decision workflow |
What may enter state |
input contracts |
| What to gather first | evidence collection |
| Atomic rules | policy checks |
| Act / review / abstain | confidence thresholds |
| Reviewer payload | human handoff |
| What to persist | audit trail |
| How it breaks | failure modes |
| Labeled replay | you are here |
| Shadow → canary | production rollout |
FAQ
Will jev.pro publish a leaderboard for this use case? No. Measure on your labels. Vendor cookbook figures stay labeled as vendor claims.
What must stay frozen? Questions, criteria, and the pinned model id. Aliases can move.
Where is the rest of the KYC pack? Start with KYC failure modes and KYC production rollout. Cluster hub: Use cases.
Can Jev replace Jumio / Onfido / our list provider? No. Keep the vendor of record. This page is leftover text triage. See Jev vs KYC vendors.
Is this legal advice or a KYC certification? No. Unofficial field notes. Counsel and your program own attestation.
What this page does not claim
- Not a substitute for KYC/AML programs.
- No pass-rate or false-accept claims.
- Not official TypeSafe.
- Official TypeSafe status, or that jev.pro issues API keys.
- That a schema-constrained answer is automatically factually correct.
Disclaimer
This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai.
Primary documentation: https://docs.typesafe.ai. Hub: Use cases.
Sources
Public TypeSafe or adjacent documentation only. No private claims.