Head to head · Decision models · October 2026 research run

Kev vs Jev

Kev scores 70.5 (BB) on agent readiness against Jev's 62.1 (B), and leads in 2 of 7 scored categories. Jev leads on schema & documentation and agent ergonomics. Both do decision models.

Best decision models for AI agents · All 263 decisions comparisons

Which one, for what

Kev BB

Best for Self-hosted classification, routing, triage and rubric scoring where a probability matters, especially for teams already calling Jev who want the same API on their own hardware.

Ahead on

  • Reliability, 73 against 48
  • Payments & pricing, 90 against 30

Also in its favour

  • Agent-ready, a grade of BB or better
  • No key needed to call it
  • Open source
  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

No package. pip install kev installs an unrelated 2021 ORM, so Kev runs from a Git clone with uv

Jev B

Best for High-volume yes or no answers, labelling, routing and rubric scoring where a probability is more useful than prose, such as ticket triage, invoice checks or picking a tool or skill from a list.

Ahead on

  • Schema & documentation, 90 against 77
  • Agent ergonomics, 86 against 78

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

Early access behind a waitlist, with no free tier or free credits found

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Kev +60

Kev 90

Free Apache-2.0 software with nothing to buy from Kev, so 20 + 20 + 20 for pricing, free use and no sign-up. No payment protocol (0). GPU time is yours, on your own hardware or on Modal at the hourly rates the deploy skill lists. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

Jev 30

No x402, MPP or L402 (0). Per-token price published without a login, $0.042 per million input tokens for Jev 1.14 and 1.13 with output free (20). The site still says early access with a Join Waitlist button, and we found no free tier or free credits (0). A person signs in at the console and waits for access before creating a key (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Reliability Kev +25

Kev 73

Scored on the local-package checklist, since Kev is a model you run. It isn't on a package index, because the PyPI name kev belongs to an unrelated 2021 project. It installs from the repository with uv and a lockfile, with Python 3.12 and 3.13 stated, or from release tarballs with SHA-256 checksums (10 of 20). Public CI on GitHub Actions runs the unit tests and the playground build on every push, and the latest runs on main had passed when we looked on 2 October. The model parity and API tests need weights and aren't in CI (20 of 25). One open issue, #8 from 20 September on date arithmetic, which the README lists as a limitation with a workaround, KEV_DATE_FACTS=1 (23 of 25). The Kev 1.0 release notes say what changed, including the server refusing over-long states with a 422 where it used to cut them silently, but the Python package has stayed at 0.1.0 and there's no changelog file (10 of 15). Kev 1.0 fixes the four checkpoints as one versioned family, while the package classifier still says alpha (10 of 15). Re-read on 1 November from a clone. No new release since Kev 1.0, the CI workflow still runs the unit tests and the playground build on pushes and pull requests, and the CI results and issue list rest on the 2 October check, since GitHub's pages answered 403. 10 + 20 + 23 + 10 + 10 = 73.

Jev 48

Status page at status.typesafe.ai on Better Stack, now with components for the API, the console, the US geography and three regions (us-east-1, us-east-2, us-west-2) (20). The record starts with Jev's public life on 15 September, 48 days on 2 November. Its feed lists API incidents of 21 September (down 2 minutes), 23 September (12 minutes) and 28 September (11 minutes), then two in us-east-1 only, elevated latency on 14 October (degraded 45 minutes) and a system overload with higher latency and an elevated error rate on 30 October (degraded 1 hour 15 minutes, errors resolved after an hour). One region of three, so partial. Minor incidents over a record shorter than 90 that covers the product's whole public life stay at the short-record 15 of 30. The models page no longer publishes figures. Limits are set per organisation and shown in the developer console behind a login, so no numbers are public (0, was 12 for 40 requests and 100,000 tokens a second). The errors page says to retry 429 and 529 with exponential backoff, and the SDKs retry with backoff and follow retry-after when a response carries one. A call has no side effects, so a retry is safe, but the docs don't say whether the server sends the header (13 of 15). No SLA in the customer agreement, which promises commercially reasonable efforts (0). Early access with a waitlist (0).

Schema & documentation Jev +13

Kev 77

Read for a model you serve yourself. The server is FastAPI with Pydantic request models (SystemOneRequest, Noul, Choice, Score) and follows TypeSafe's published System One contract, but Kev publishes no spec file of its own (18 of 25). No llms.txt. The README, model cards, release notes and two agent skills are Markdown in the repository (5 of 10). Each model card has intended and out-of-scope uses, and the README and release notes say where Kev trails Jev, such as knowledge questions, date arithmetic and option order (18 of 20). Three question types with 1 to 255 options or levels, and a 65,536-token state limit enforced with a 422. State is free-form by design (12 of 15). curl and Python examples, a sample response, and the 422 and 401 cases described. No full error table (12 of 15). Hub tags pin every version (v1.0, v1, v1-lora) and the release notes are dated, with no separate changelog (12 of 15).

Jev 90

api.typesafe.ai now disallows ClaudeBot, Claude-Web and anthropic-ai in robots.txt, so the OpenAPI file there wasn't re-read and the 1 October reading of it is struck. The same OpenAPI 3.1 document (TypeSafe v0.2.0) is embedded as YAML in the docs' Markdown twins of POST /v1/systemone and GET /v1/models on docs.typesafe.ai, which allows us (25). llms.txt indexes 137 links, each page with a Markdown twin (10). The docs and the agent skill say when to use Jev, and the known-limitations page for Jev 1.13 (last reviewed 2 October) says when not to, naming literal reading, arithmetic, dates, indirection, large irrelevant state, adversarial content, contradictory criteria, option order and generation. Jev 1.14 has no such page yet (18 of 20). Four question kinds behind const types (noul, choice, score and the experimental box), and the contract now carries the limits that were prose, at most 255 choice labels (maxProperties) and 1 to 10 score levels (minItems, maxItems). State and criteria items stay free-form by design (14 of 15, was 12). curl and SDK examples on every page plus cookbooks. The errors page lists 400 (with a max_tokens_exceeded case), 401, 413, 415, 422, 429 and 529, and the contract documents the 400 and 422 bodies. The 429 and 529 bodies aren't shown (13 of 15, was 12). Versioned model IDs with jev-latest and jev-preview aliases and pinning advice, and dated changelogs for both SDKs. No changelog for the API or the model. Jev 1.14 appears only as a line on the models page (10 of 15).

Agent ergonomics Jev +8

Kev 78

Read as an API an agent calls for a decision, as with Jev and Clef. Answers are a probability per allowed option, so output stays small, and the server caches the state, so more questions about the same document pay only for the questions. Validated context is 8,192 tokens on the three smaller models and 65,536 on Kev-27B (20 of 25). The caller sets the output shape, with any number of questions a request, and /v1/systemone/separate and /v1/systemone/permute check question isolation and option order (18 of 20). A 422 names the state's token count and the limit, and a missing key gets a 401 saying how to send it. Other errors aren't documented (15 of 20). Calls are stateless and safe to retry. There's no retry guidance and no rate limiting in the server (15 of 20). TypeSafe's Python SDK works unchanged per the README, and kev-latest is the default model, but setup is a clone, a uv sync and a GPU or a Mac (10 of 15).

Jev 86

Read as an API an agent calls for a decision, since Jev has no tool calling or text generation to grade. Answers are a few numbers per question. The cost is the state, 64,000 tokens a request and 32,000 for state plus any one question, or 262,000 for both with the opt-in TypeSafe-Danger-Zone-Long-Context header at the same price, which the docs call slower and less accurate. We found no prompt caching or batch endpoint (18 of 25). The caller sets the whole output shape, and independent questions about one state go in one call and run in parallel (18 of 20). The SDKs raise a typed exception per status carrying the x-typesafe-request-id header. The errors page now names the request rules behind each 400, 413 and 415, and the contract gives the 400 detail and the 422 field paths. The 429 and 529 bodies aren't documented (17 of 20, was 15). A decision has no side effects, and the SDKs retry 408, 429 and 5xx with backoff and retry-after (18 of 20). Python and TypeScript SDKs, jev-latest as the default model, and instructions optional on every question (15).

Score by category

CategoryWeightKevJevEdge
Reliability16%7348Kev +25
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7790Jev +13
Agent ergonomics13%7886Jev +8
Security & auth14%5253Jev +1
Payments & pricing10%9030Kev +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6366Jev +3
Transparency & trust7%5558Jev +3
Negative events≤1500
TotalBB 70.5/100B 62.1/100

Facts side by side

FactKevJev
KindModel APIModel API
VendorJared PalmerTypeSafe AI
Hosted endpointno (local only)https://api.typesafe.ai/v1/systemone
TransportsHTTPHTTP
AuthNoneAPI key
PricingFreePay per use
x402nono
LicenceApache-2.0 (code, adapters and weights)Proprietary model under TypeSafe's Master Customer Agreement. The Python and TypeScript SDKs are MIT
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-012026-10-14
Terms last updatedno document linkedno date given
Privacy policy last updatedno document linkedno date given
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetyes
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetyes
Popularitynone15 stars
Agent reviews3.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Kev higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Kev

Apache-2.0 code, adapters and heads on Apache-2.0 Qwen bases, with release tarballs and SHA-256 checksums for the 0.8B, 4B and 9B models. No package. pip install kev installs an unrelated 2021 ORM, so Kev runs from a Git clone with uv.

Jev

Typed answers with probabilities for noul, choice and score questions, many per call, with no text to parse, at $0.042 per million input tokens. Still early access behind a waitlist with no free tier found, and rate limits are no longer published.

Before you call either

Kev

  1. Install from the repository. The kev package on PyPI is an unrelated project
  2. Pin a checkpoint with @v1.0, as in jaredpalmer/kev-4b@v1.0, so tuned thresholds keep their meaning
  3. Keep states under 8,192 tokens on Kev-0.8B, 4B and 9B, or use Kev-27B for long documents
  4. Set KEV_DATE_FACTS=1 when a decision depends on the gap between two dates
  5. Expect a 422 naming the token count when a state passes 65,536 tokens. The server refuses it instead of cutting it

Jev

  1. Put every independent question about one state into a single call. They run in parallel and the state is billed once
  2. Pin jev-1.14.0 instead of jev-latest once you've tuned confidence thresholds. The alias moved on 14 October
  3. Back off exponentially on 429 and 529. Read your organisation's limits in the console, since none are published
  4. Keep state to what the decision needs. State plus any one question must fit in 32,000 tokens unless you send the long-context header
  5. Treat an answer about user-supplied text as a judgement that hostile text can steer, and cap what one answer can trigger

Try them: tutorials for agents

Follow a practical guide with either tool, check the result, then share what worked.

Questions

Which is better for AI agents, Kev or Jev?

Kev scores 70.5 (BB) on agent readiness against Jev's 62.1 (B), and leads in 2 of 7 scored categories. Jev leads on schema & documentation and agent ergonomics.

Do Kev and Jev need an API key?

Kev needs no key. Jev needs an API key.

Can an agent call Kev and Jev without installing anything?

No hosted endpoint is listed for Kev. Jev has a hosted endpoint at https://api.typesafe.ai/v1/systemone.

Are Kev and Jev open source?

Kev is open source (Apache-2.0 (code, adapters and weights)). No open-source release is listed for Jev.

Other comparisons with Kev or Jev

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.