Jev versus keyword triage: a practical comparison
Keyword triage is if "chargeback" in text. It is fast, cheap, and fails on synonyms. Jev handles the synonym problem and fails on exact identifiers you should have regexed.
Independent. Official jaggedness: do not ask the model to count or to parse what a regex can find. docs.typesafe.ai.
Comparison scope
This page is first-touch routing language, not full moderation (see content filters / moderation APIs).
Criteria that decide the architecture
| Axis | Jev (System One) | Keyword triage |
|---|---|---|
| Paraphrase | Wins | Misses |
| Order id / IBAN / CVE | Do not use Jev | Wins |
| Adversarial misspellings | Test; not a security product | Also fragile |
| Cost | Tokens (vendor $) | CPU |
Decision quality and control
Keyword lists are inspectable. Jev criteria are inspectable too — if you wrote them. Hidden prompt piles are not. Prefer short criteria over a 4k-word “be a senior agent” essay.
Integration trade-offs
Pipeline: normalize → regex extract → if leftover uncertainty, Jev Choice with an other. Never skip regex for things code can match exactly.
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
- Users never use your canonical words
Prefer Keyword triage when
- The token is an identifier or a legal exact phrase
Keywords first, Jev on the remainder. Same advice as traditional routing.
What this page does not claim
-
No recall@k vs keywords.
-
Schema-safe output is not the same as factual correctness.
-
No independent bake-off numbers live here.
FAQ
Multilingual keywords? Lists explode. Jev may help; English is strongest per TypeSafe. Test.
Should I log matched keywords and Jev? Yes — two channels, one ticket.
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 ticket queues, vs content filters, intent routing. Canonical: https://docs.typesafe.ai.
Sources
Public TypeSafe or adjacent documentation only. No private claims.