SPEV vs Strands Decider 2B

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.

Strands Decider 2B

A 1.9B-parameter Apache-2.0 decision model that runs on a laptop GPU, an Apple silicon Mac or a CPU, with its training data, recipe and per-version results published. It's an experimental 0.1.0 release with a 4,096-token window that cuts long states by default, and its local server has no authentication.

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

Strands Decider 2B

1. Pin the checkpoint by its full name, such as StrandsAgents/strands-decider-2B-hobson-v21, since each version is a separate Hugging Face repository
2. Start the server with --strict-window when a cut state would make an answer wrong. It then returns 422 naming the window
3. Ask every question about one state in one request. The state is read once and each question adds only its own tokens
4. Keep the server on 127.0.0.1 or put an authenticating proxy in front. It has no key option
5. Measure thresholds on your own traffic before acting automatically. The card says confidence bands hold for short classification only