Use cases· Last updated

KYC input contracts 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 input contracts slice of the KYC residual-text decisions pack. Intent: apply the Jev (TypeSafe System One) decision model to KYC residual-text decisions input contracts. Primary search language: KYC Jev input contracts. 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

An input contract is the allow-list of fields you will ever POST for KYC residual-text decisions. It is a decision contract for the application narrative + vendor result summary: if a field is not named in instructions, it should not be in state. That is how you beat noisy “dump the object” integrations — the rival-intent failure mode — without cloning anyone’s IA.

Hub: Use cases. Compare, when the other tool is the real job: KYC vendors.

Input Contracts inputs

Documented System One inputs: state (string, object, or array of text) and a questions map. English is the primary training language. Images, audio, and video are not accepted.

Allow for KYC residual-text decisions:

{
  "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." }
}

Bind paths: application.narrative, vendor.country_claimed, policy.consistency.

Refuse at the wrapper (do not send):

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.

Decision signals and actions

The contract exists so each primitive stays atomic:

Id Type Job
narrative_consistent Noul Does application.narrative contradict vendor.country_claimed / policy.consistency?
packet_complete Score Does the text packet look complete enough for a human KYC review?
residual Choice proceed_vendor / hold_text / escalate_compliance / other

If a new CRM field appears, either add a question that names it or drop it. Do not “just include it.” 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

Contracts are a guardrail: missing required text → do not call Jev (or ask a Noul “is enough information present?”). That is cheaper than a confident wrong narrative_consistent. 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

Version the contract (field list + criteria git SHA) next to the pinned model. Replay hold / proceed / escalate gold from KYC analysts, plus contradiction gold when either changes. 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 you are here
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 evaluation
Shadow → canary production rollout

FAQ

What happens if I send the whole warehouse row? jev-1.13 loses accuracy as distractors grow (official jaggedness note). Drop ID photos, selfies, or liveness video (not accepted). 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.

Can I send images of the artifact? No. State is text (string, object, or array of text). Transcribe first.

Where is the rest of the KYC pack? Start with KYC decision workflow and KYC evidence collection. 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

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.