Kev vs Drex 1.5

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.

Drex 1.5

The hosted endpoint has a public OpenAPI document, published limits and pinned model versions, at $0.05 per million input tokens with no output charge. The #1 under 10B claim rests on Nace's own run, since Drex is absent from both public boards. Weights carry Open RAIL-M, which requires a commercial licence above $1 million in revenue or funding.

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

Drex 1.5

1. Call https://console.nace.ai/v1/systemone with Authorization: Bearer nace_sk_..., and pin model drex-v1.5 rather than drex-latest in production.
2. Stop on 402 insufficient_credit or 402 payment_required until credit is topped up or the unpaid invoice is paid.
3. Retry 429 and 529 after retry-after-ms. On a 422 for an unknown model, use one of the ids the error message lists.
4. Keep state below 131,072 tokens and the body below 1,048,576 bytes, and send at most 512 questions per request.
5. Keep the key on a server. A key in browser code is exposed, and the /v1 routes send no Access-Control-Allow-Origin header.
6. Check usage.input_tokens and the usage CSV after retries, since /v1/systemone documents no idempotency key.