Laya vs Drex 1.5

Laya

Apache-2.0 code and weights, installed with pip install laya, with Python 3.10 to 3.13 tested in CI. Base checkpoints score 0.362 and 0.352 on the maintainers' typed-decisions benchmark against a 0.318 random baseline, so it needs fine-tuning.

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.

Laya

1. Set LAYA_API_KEY before starting laya-serve. It listens on every interface by default
2. Gate on answer_confidence, not confidence, which measures entropy and doesn't match Jev's field
3. Shortlist choice questions with more than about 20 options using predict_shortlist or the laya_shortlist tool
4. Use semantic or opaque labels such as A and B, not yes and no, in choice questions. The checkpoints can follow the label text
5. Pass model="multilingual" and max_len=8192 for long documents. The English checkpoint stops at 512 tokens

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.