gpt-oss-20b-tq3
manjunathshiva基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
From language to images, open weights to APIs. Understand capabilities and compare real costs.
Find the right engine for your next idea.
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
**Open, calibrated System 1 decision model.** Give it a **state** (text, email, ticket or JSON) and **typed questions** (`choice`, `score`, `noul`); it returns a calibrated probability for every option in a single forward pass: **17 ms on an NVIDIA L40S, 18 ms on an Apple M4 Max, ~9 ms per question batched**. ~400M parameters, Apache-2.0. It never generates text, so there is nothing to parse and nothing to hallucinate. **Ahead of Laya like for like on typed-decisions: 0.796**, against 0.766 for Laya's typed-decisions checkpoint (+0.030, 95% CI +0.014 to +0.044), both fine-tuned on its train split. TypeSafe Jev scores 0.754 there zero-shot (measured through TypeSafe's own API): a reference, not a head-to-head. **Documentation: manjunathshiva.github.io/opendecider**: getting started, choosing a model, guides for serving, LM Studio, Ollama and vLLM and automating the confident decisions, plus the Python and HTTP API reference.
GGUF builds of OpenDecider-small, the 4B OpenDecider decision model, for **LM Studio**, **Ollama** and anything else built on llama.cpp. Best for decisions it has never seen: the best general accuracy and calibration of the 4B models (zero-shot on typed-decisions). A decision model answers typed questions (`choice`, `score`, yes/no) about any text or JSON with a probability for every option, instead of generating text. The opendecider package builds the exact prompt the model was trained on and reads the option probabilities from the server's token log-probabilities. On typed-decisions (2,000 questions), the Q8_0 build gives the same top answer as the full-precision model on 1,975 (98.8%), at the same accuracy: Measured through Ollama's llama.cpp engine; LM Studio runs the same engine and returned identical log-probabilities on the same file. **Q8_0 is the recommended file**; Q4_K_M is for machines with little memory.
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
Adjust provider, category or input/output filters. New models are added continuously.
Adjust monthly token usage to compare estimated API costs.
Uses collected, comparable USD-per-million-token rates. Snapshots exclude cache discounts, tiers, extra reasoning output and taxes. Check current source prices.
Separate input, output and cache rates, then estimate the same workload. Image, audio and video rates may use items, duration or resolution rather than tokens.
Not necessarily. Check each version’s license, commercial restrictions and policies. Self-hosting also incurs compute and maintenance costs.
Rankings depend on tasks, versions and methods. Compare accuracy, latency, reliability and costs on your own workload.