Comparisons· Last updated

Jev versus static forms: a practical comparison

A static form forces the user into dropdowns you trust. Jev is useful when they still paste a paragraph in “anything else?” — or when the form was skipped entirely (email, chat).

Independent comparison. Official state guidance: send structured fields when you have them; filter distractors. docs.typesafe.ai. No keys from this site.

Comparison scope

If the decision is “which dropdown did they pick?”, you do not need a model. If the decision is “does this comment change the queue?”, that is a Noul/Choice on leftover text.

Criteria that decide the architecture

Axis Jev (System One) Static forms
Source of truth Probabilities over text User-submitted fields
Validation None — your schema around the POST HTML / JSON schema
Missing values not_stated option if you add it Required fields
UX Invisible backend The product surface

Decision quality and control

Forms prevent the ambiguity Jev then has to resolve. Every field you can require is a field you should not spend tokens on. Jaggedness: large irrelevant state hurts accuracy — dumping the entire CRM record next to a one-line comment is how you pay more for a worse answer.

Integration trade-offs

Build state from form JSON plus the free-text field only. Name paths in instructions with backticks. Keep file uploads as extracted text; Jev does not take images.

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

Prefer Static forms when

Form first, Jev on remainder. Do not replace checkout or KYC forms with a 20-way Choice.

What this page does not claim

FAQ

Can Jev invent form fields? No generation. Extract candidates in code or with an LLM, then Choice.

Multilingual forms? English is TypeSafe’s primary training language. Test other languages yourself; watch confidence.

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 manual review, vs legal intake, state and memory. Canonical: https://docs.typesafe.ai.

Sources

Public TypeSafe or adjacent documentation only. No private claims.