SAVRN
Search Contact SAVRN

Open-weight model · Text classification

decider-4b-fp8

by LLM Tech llmtech/decider-4b-fp8

decider-4b-fp8 is an open-weight model for text classification from LLM Tech, released under Apache License 2.0. It has 4.2B parameters and a 262,144-token context. At 16-bit it needs about 10.1 GB of GPU memory, which fits on 1x MI300X from $1.85 an hour, at the lowest prices in the SAVRN Index.

Mapika/decider-4b v2.1 quantized to FP8 for vLLM: FP8 E4M3 weights with one scale per output channel and FP8 activations scaled per token at run time. 4.85 GB against 8.41 GB for the bf16 checkpoint.

Parameters4.2B
Context262,144
Weights4.8 GB
Licenseapache-2.0
AccessOpen weights
Monthly Downloads—

Runs On

What it takes to serve decider-4b-fp8 (4.2B parameters): the memory its weights need at each precision, and the cheapest way to rent enough data-center GPUs to hold them.

PrecisionWeightsMemory neededCheapest setupPer hourAlso fits
16-bit 8.4 GB 10.1 GB 1x MI300X (192 GB)
Vultr
$1.85 1x H100 $1.99 · 1x MI325X $2.00
8-bit 4.2 GB 5.0 GB 1x MI300X (192 GB)
Vultr
$1.85 1x H100 $1.99 · 1x MI325X $2.00
4-bit 2.1 GB 2.5 GB 1x MI300X (192 GB)
Vultr
$1.85 1x H100 $1.99 · 1x MI325X $2.00

Memory is the weights at that precision plus 20% for the runtime and a short context; a long context needs more. Prices are the lowest on-demand hourly rates in the SAVRN Index, read Oct 1, 2026.

decider-4b-fp8 on every accelerator the SAVRN Index prices, at every precision

Model Card

By LLM Tech, published under apache-2.0, revision c69c18f50efd.

Mapika/decider-4b v2.1 quantized to FP8 for vLLM: FP8 E4M3 weights with one scale per output channel and FP8 activations scaled per token at run time. 4.85 GB against 8.41 GB for the bf16 checkpoint. Quantized and measured by LLM Tech; the model, its training and its evaluation protocol are Mapika's. Read the bf16 card for what the model is and how it was trained. The base revision is eb5fbdfc9448473ec25e399882912863afbdb70e. Tokenizer, chat template, generation config and deciderconfig.json (temperatures included) are the author's files unchanged, apart from the version and quantization fields. Both models were run through vLLM 0.29.0 on the same rows: the author's regression set rebuilt…

Read LLM Tech's full model card

Mapika/decider-4b v2.1 quantized to FP8 for vLLM: FP8 E4M3 weights with one scale per output channel and FP8 activations scaled per token at run time. 4.85 GB against 8.41 GB for the bf16 checkpoint. Quantized and measured by LLM Tech; the model, its training and its evaluation protocol are Mapika's. Read the bf16 card for what the model is and how it was trained.

The base revision is eb5fbdfc9448473ec25e399882912863afbdb70e. Tokenizer, chat template, generation config and decider_config.json (temperatures included) are the author's files unchanged, apart from the version and quantization fields.

Accuracy against the bf16 weights

Both models were run through vLLM 0.29.0 on the same rows: the author's regression set rebuilt from public data (95 tasks, 67 in-task and 28 held-out, 144,226 rows, plain state-first layout, the author's temperature map) and the 231 public JevBench items. Our bf16 run matches the author's published regression accuracy and NLL within 0.0005 (in-task 0.8308 / 0.4145 NLL, held-out 0.7838 / 0.5689 in eval_results.json).

in-task acc / NLL / ECE (67 tasks) held-out acc / NLL / ECE (28 tasks) JevBench easy / standard / hard
bf16 0.8308 / 0.4146 / 0.0302 0.7837 / 0.5686 / 0.0773 48/48, 71/72, 73/111
FP8 0.8300 / 0.4157 / 0.0311 0.7823 / 0.5709 / 0.0788 48/48, 71/72, 74/111

Accuracy moves by -0.1 points in-task and -0.1 held-out; NLL by +0.0011 and +0.0023. Per task: lower on 44, higher on 34, equal on 17; the largest drops are fin_phrasebank (-1.2, 970 rows), commonsense_qa (-0.9, 1221 rows), openbookqa (-0.8, 500 rows), wic (-0.8, 638 rows). The public JevBench tiers are 48, 72 and 111 items; differences of one to three items are within their noise.

Speed

vLLM 0.29.0 on one RTX PRO 6000 Blackwell Server Edition (96 GB), prefix caching off, one output token per row, unique random states. Prefill throughput is the best over batch sizes 1 to 64; latency is one request alone.

state length bf16 tokens/s FP8 tokens/s bf16 latency FP8 latency
1,024 38,941 56,393 (x1.45) 34 ms 24 ms
8,192 36,724 52,205 (x1.42) 228 ms 160 ms
32,768 30,699 40,786 (x1.33) 1082 ms 817 ms

Usage

The author's package serves this checkpoint as is. decider.serve_vllm exposes POST /v1/systemone, the System One request shape (TypeSafe's Jev format):

pip install "decider-ai[serve]==1.6.0" vllm==0.29.0 ninja   # vLLM builds kernels with ninja on first start
DECIDER_MODEL=llmtech/decider-4b-fp8 uvicorn decider.serve_vllm:app --port 8000
curl -s localhost:8000/v1/systemone -H 'content-type: application/json' -d '{
  "model": "decider",
  "state": "My card was charged twice for the same purchase.",
  "questions": {
    "dept": {"type": "choice", "instructions": "Which department should handle this?",
             "criteria": {"billing": null, "technical support": null, "sales": null}},
    "refund": {"type": "noul", "instructions": "Does this need a refund action?"}
  }
}'

The checkpoint was run only through vLLM 0.29.0 on Blackwell (SM120) here.

What is quantized

llm-compressor 0.14.0, scheme FP8_DYNAMIC, no calibration data. The same modules as in the author's NVFP4 recipe stay in bf16.

kept in bf16 quantized
embed_tokens, lm_head, linear_attn.conv1d, linear_attn.in_proj_a, linear_attn.in_proj_b, norms attention q_proj, k_proj, v_proj, o_proj; delta-net in_proj_qkv, in_proj_z, out_proj; MLP gate_proj, up_proj, down_proj (200 linear layers)

The KV cache is not quantized.

Limitations

  • Everything in the bf16 card applies.
  • The quantization costs 0.1 points in-task and 0.1 held-out against bf16 in the same engine.
  • Only the regression set and the public JevBench items were re-measured; the OpenJev, Mind2Web, browser, game and Bespoke numbers of the bf16 card were not.
  • Measured with vLLM 0.29.0 on RTX PRO 6000 Blackwell only; not with TensorRT-LLM or SGLang.

About

Quantized and measured by LLM Tech; questions go to the Community tab. Model: Apache 2.0, by Mapika (GitHub).

Configuration

Architecture
Qwen3_5ForCausalLM
Context length (tokens)
262,144
Layers
32
Hidden size
2,560
Feed-forward size
9,216
Attention heads
16
Key/value heads
4
Head dimension
256
Vocabulary size
248,320
Model type
qwen3_5_text
Quantization
compressed-tensors

Identity and Version

Repository
llmtech/decider-4b-fp8
Publisher
LLM Tech
Task
Text classification
Modality
Text
Library
Not stated by the source
Parameters
4.2B parameters
Languages
en
Revision
c69c18f50efdf7cf186bf93ef99269d92b165451
First published
2026-09-28
Last updated
2026-09-28

Files and Weights

10 files, 4.9 GB in total. The weights are 1 file totalling 4.8 GB in safetensors.

Weights1 file · 4.8 GB
Configuration4 files · 8.4 KB
Tokenizer2 files · 20.0 MB
Documentation1 file · 4.7 KB
Other1 file · 7.8 KB
Repository1 file · 1.6 KB
Every file
FileTypeSizeSHA-256
model.safetensorsWeights4.8 GB 1db8cbc7afbb
config.jsonConfiguration6.2 KB —
decider_config.jsonConfiguration1.6 KB —
generation_config.jsonConfiguration116 B —
recipe.yamlConfiguration408 B —
README.mdDocumentation4.7 KB —
chat_template.jinjaOther7.8 KB —
.gitattributesRepository1.6 KB —
tokenizer.jsonTokenizer20.0 MB 06b9509352d2
tokenizer_config.jsonTokenizer1.1 KB —

License and Download

License
apache-2.0
Access
Open weights, no gate
Download size
4.8 GB
Download from LLM Tech

Released by LLM Tech through its official repository on Hugging Face. Read the license.

Built From

  • Derived from Mapika/decider-4b
  • Quantized from Mapika/decider-4b

Memory Requirements

PrecisionWeights in memory
As published4.8 GB
16-bit8.4 GB
8-bit4.2 GB
4-bit2.1 GB

Weights only, from the published parameter count; the key-value cache and runtime add to this.

Questions About decider-4b-fp8

How much GPU memory does decider-4b-fp8 need?

About 10.1 GB at 16-bit and 2.5 GB at 4-bit: the weights (4.2B parameters) plus a working margin. A long context needs more.

What is the cheapest GPU to run decider-4b-fp8 on?

At 16-bit, 1x MI300X from $1.85 an hour; at 4-bit, 1x MI300X from $1.85 an hour, at the lowest on-demand prices the SAVRN Index lists.

Can I use decider-4b-fp8 commercially?

Yes. decider-4b-fp8 is released under Apache License 2.0. The Apache License 2.0 is a permissive open-source license. It permits commercial use, modification and redistribution. It requires keeping the license and copyright notices and any NOTICE file, stating significant changes, and it includes an express patent grant from contributors.

What is decider-4b-fp8's context length?

262,144 tokens, from the maximum position embeddings in its published configuration.

Similar Models

Model · Text classification

blink-4b

Govind Kamtamneni

Small, fast decisions for routing and checks at volume. Send text or JSON state with choice, noul (yes/no), or score questions. Get a probability for every offered answer, not generated text. Each batch takes one forward pass; large requests can use several batches. Use choice to route a request, noul for a yes/no check, or score for an ordered rating. The same call can ask several questions about a single state. Try it: POST /v1/systemone, GET /v1/models, and GET /healthz. Point TypeSafe's server-side Python or JavaScript SDKs at it with TYPESAFEBASEURL; text decisions use the same request and response fields as hosted Jev. Requests run one at a time by default; --batch-window-ms 5 enables…

Open weights other 4.2B parameters 262,144 tokens transformers

Model · Text classification

Kev-4B-MLX-Serve-8bit

Alin C Selea

Kev-4B (a LoRA on Qwen3.5-4B-Base with a pointer head) packed for mlx-serve's POST /v1/decisions. Kev answers typed questions about a piece of text (choice, noul, score) with calibrated probabilities. It never generates text. The pack folds the LoRA into the base the way kev does on MLX, quantizes the trunk to 8-bit (affine, group 64; a bf16 build comes from --q-bits 0), and stores the pointer head as kevhead.safetensors with the calibration temperature in kevconfig.json. No PyTorch or pickle file is needed to serve it. Built with tests/convertkevweights.py from the mlx-serve repo. Kev and Qwen3.5 are Apache-2.0.

Open weights apache-2.0 4.2B parameters 262,144 tokens mlx-serve

Model · Text classification

Qwen3-Reranker-4B-W4A16-G128

Mou Geren

GPTQ Quantized Qwen/Qwen3-Reranker-4B with Ultrachat, THUIR/T2Ranking and m-a-p/COIG-CQIA for calibration set. VRAM Usage: 17430M -> 11000M (w/o FA2, according to Embedding model's result). I think <5% accuracy, further evaluation on the way... The Embedding one shows ~0.7%. pip install compressed-tensors optimum and auto-gptq / gptqmodel, then goto the official usage guide.

Open weights apache-2.0 4.1B parameters 40,960 tokens transformers

Model · Text classification

VirbiusGuard-4B

Min Cai

VirbiusAgent 安全分类器(Prompt L1 检测),基于 Qwen3Guard-Gen-4B 微调的 LoRA 模型。 输出严格 JSON:hitrule 与 triggeredid。 同口径评测相对基座:漏检 15.4% 降到 0.8%(gold1000 / V15),jailbreak 召回 57.1% 升到 100%。 0.6B 轻量版:https://www.modelscope.cn/models/i1see1you/VirbiusGuard 基座用官方 Safety 模板(Unsafe / Controversial 视为拦截);VirbiusGuard-4B 用引擎 JSON 协议。评测集与口径相同。 评测集:data/eval/gold1000.jsonl(615 unsafe / 385 safe)。误报 = FP / 385。 基座漏掉的主要是越狱与 Agent 工具滥用。V13.3 召回拉满但误报过高;V15 起进入可用区。V17 误报最低,但召回/自伤回退。 - 架构:Qwen3ForCausalLM(4B),LoRA(rank 32 / alpha 64) - 基座:Qwen3Guard-Gen-4B - 相对基座的补强:jailbreak 与 agent-behavior - V17 数据:与 0.6B V15 同口径,良性切片再平衡,含 oasst1、COIG 中文散文、OCR 风格文本 输出 10 种 unsafe 类别(triggeredid)或 safe(hitrule 为 false)。每条输入只输出一个主要类别:…

Open weights apache-2.0 4B parameters 32,768 tokens transformers

Model · Text classification

OpenJudgement-4B-Preview

Kitani

Experimental open-weights judgment model by Kitani OpenJudgement is unfinished. We're releasing this checkpoint for people to experiment with, inspect, and build on. It still needs work on judgment quality, calibration, and inference efficiency. It is not as good as Jev overall in our internal task comparisons. It does show a meaningful improvement over untouched Qwen on our recorded validation comparison: 75.4% versus 64.2% annotation agreement. That is a result on a particular evaluation set, not a claim that we beat the base model on every task. There are questions it handles well and questions it confidently gets wrong. Please judge the preview by your own examples rather than assuming…

Open weights apache-2.0 4.5B parameters 262,144 tokens transformers

Model · Text classification

metask-jev-4b-policy-mix

Raymond wei

A calibrated typed-decision model: give it a state (text, ticket, policy, JSON) and a typed question — choice, boolean, or rubric score — and it returns a probability for every option in a single forward pass (~24 ms). No generation, no parsing, nothing to hallucinate. 12 of 13 subsets exceed Bespoke Nimble-9B — a model 2.2× its size — same prompt format, same scoring protocol. The primary suite: BoolQ, MultiNLI, PAWS, PubMedQA, SQuAD-2, VitaminC, Civil Comments, Aegis 2.0, MASSIVE (en/de), HelpSteer-2, SummEval (consistency / relevance). Every item human-labeled; byte-reproducible (manifest-locked ids + sha256); same protocol as the Bespoke Nimble evaluation. Wins: verification-style noul…

Open weights apache-2.0 4.5B parameters 262,144 tokens transformers