Drex 1.5 vs SPEV

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.

SPEV

SPEV answers typed questions over text, audio or an image in one call, with a public OpenAPI schema and Apache-2.0 weights on Hugging Face. It is a day old, has an 8,192-token context, no status page or changelog, and Sprag's terms let it train on API content unless the customer opts out by email.

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.

SPEV

1. Send model: "spev" to POST https://api.sprag.ai/v1/decisions with a bearer key. /v1/systemone returns 410
2. Ask every question about one piece of evidence in one request. Answers come back in question order
3. Send audio as base64 in input_audio with format, not as a data URL, and at most one image across all messages
4. Keep evidence and questions under 8,192 tokens. Over the limit returns 400 model_limit_exceeded
5. Back off on 429 and 503 for Retry-After seconds. Limits are 60 requests a minute per organisation by default
6. Handle an answer of type refusal, which carries no probabilities