LFM3-Audio-2B-GGUF
AtomicChat基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
Input Audio · Text→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗DISCOVER & COMPARE
Explore AI models 84991
LFM3-Omni-2B-GGUF
AtomicChat基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
Input Not verified→ Output Not verified
Price not verifiedCheck multimodal and channel pricing separately
View details ↗LFM3-VL-2B-GGUF
AtomicChat基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
Input Text · Image→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗Ling-3.0-flash-GGUF
AtomicChatLing 3.0 flash is a 124B MoE with 5.1B active parameters; its GGUF chat template includes thinking mode and tool calling. Our AD layouts have 31–41% lower mean KL than stock llama.cpp presets at comparable sizes. The raw measurements and controls are public. From the team behind Atomic Chat , the local AI app for chat and agents. These Ling files require our TurboQuant build; use the CLI instructions below . The tests documented below cover the CLI workflow, not app compatibility. Quantizations of `inclusionAI/Ling-3.0-flash`: 124B total, 5.1B active, hybrid linear attention (35 KDA blocks interleaved 5:1 with 7 gated MLA blocks) over a 512-expert MoE. Bits are placed by hand rather than by the default rules, and the controls that prove it is worth something are published next to the files. At the same size, our layout sits 31 to 41 % closer to BF16 than what `llama-quantize` produces on its own
Input Text→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗Ling-3.0-flash-NVFP4-GGUF
AtomicChat基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
Input Text→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗Ling-3.0-flash-Sante-GGUF
AtomicChatBuilt from inclusionAI's original weights with our own importance matrix. The calibration corpora behind our builds are public. You can now run Ling in Atomic Chat . See our quantization analysis below for measurements and instructions. Every number below is measured, not estimated. How we measured it is at the bottom, and the raw logs are in the metrics repo so you can check any of it yourself.
Input Text→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗Ling-3.0-flash-Sante-Uncensored-GGUF
AtomicChat基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
Input Text→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗Ling-3.0-flash-VL-GGUF
AtomicChat基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
Input Text · Image→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗Ling-3.1-flash-GGUF
AtomicChat基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
Input Text→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗Ling-3.1-flash-Uncensored-GGUF
AtomicChat基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
Input Text→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗MiniCPM-V-4.7-1B-GGUF
AtomicChatBuilt from openbmb's original weights with our own importance matrix. The calibration corpora behind our builds are public. You can now run MiniCPM in Atomic Chat . See our quantization analysis below for measurements and instructions. Every number below is measured, not estimated. How we measured it is at the bottom, and the raw logs are in the metrics repo so you can check any of it yourself.
Input Text · Image→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗MiniCPM-V-4.7-35B-A3B-GGUF
AtomicChatBuilt from openbmb's original weights with our own importance matrix. The calibration corpora behind our builds are public. You can now run MiniCPM in Atomic Chat . See our quantization analysis below for measurements and instructions. Every number below is measured, not estimated. How we measured it is at the bottom, and the raw logs are in the metrics repo so you can check any of it yourself.
Input Text · Image→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗MiniCPM-V-4.7-35B-A3B-Uncensored-GGUF
AtomicChatOne refusal direction projected out of OpenBMB's original weights, shipped two ways: three baked GGUF builds, and a 106 MB LoRA adapter for the MiniCPM-V 4.7 quants you already have. The measurements behind this card are public. On held-out prompts, refusals fall from 96.3% to 0% in English, and from 13 of 30 to none with thinking on. MMLU moves by 0.25 points, inside the noise. You can now run the Uncensored MiniCPM-V 4.7 in Atomic Chat , locally on your own machine. The 20.1 GB build matches the original's token choice 94.5% of the time; our quant of the unmodified model at the same size does 94.9%. Already running our MiniCPM-V 4.7 quants ? Add the adapter with --lora-scaled instead of downloading a new model. *28 Oct 2026: each build is now a single file instead of 11 to 16 shards of 2 GB. The weights are unchanged (tensor-for-tensor identical).*
Input Text · Image→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗MiniMax-M3.1-Flash-GGUF
AtomicChat基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
Input Text · Image→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗Muse-Glimmer-30B-GGUF
AtomicChatGGUF builds of Meta's Muse Glimmer 30B, made from the original BF16 weights with a calibrated importance matrix and a bit layout chosen by measurement. > [!NOTE] > Support was merged into llama.cpp master in > #26841 (commit `62bf73d`). > You need a build from master — the last tagged release predates it. > [!TIP] > `AD-Q6_K` at 28.3 GB is dominated by plain `Q8_0` at 29.6 GB, which is 1.3 GB larger > and 31 % more accurate. Take `Q8_0` instead unless you need exactly that size.
Input Text · Image→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗Muse-Spark-Open-816B-A42B-GGUF
AtomicChat基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
Input Text · Image→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗Nanbeige4.3-33B-GGUF
AtomicChatGGUF quants of Nanbeige's Nanbeige4.3-33B, built from Nanbeige's original BF16 weights on release day. Nanbeige4.3-33B is Nanbeige's 33B dense agent and reasoning model (Llama architecture, 512K context, thinking on by default), Apache-2.0. You can now run Nanbeige4.3-33B in Atomic Chat , with thinking on by default. Atomic Dynamic (AD) files with our own importance matrix, from 13.7 GB to 30.1 GB on disk, plus plain Q8_0 and Q5_K_M ; every one measured against the BF16 original on one stand. > [!NOTE] > **Built on release day, 25 October.** `Q8_0` and `Q5_K_M` are llama.cpp's own > presets, made without an importance matrix; its `Q6_K` and `Q4_K_M` were up > for the first hours and are removed now that `AD-` files beat them at the same > size (their numbers stay below as the baseline). The `AD-` files > use our own importance matrix, collected on the BF16 weights (`--parse-special`) > over 8,000 chunks of 512 tokens of our calibration corpus. The corpus build was > rendered for Qwen3.8-27B, whose chat format (ChatML) Nanbeige4.3 shares; it is > `imatrix/imatrix.gguf` in the metrics repo.
Input Text→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗NVIDIA-Nemotron-3.5-Bolt-74B-A9B-GGUF
AtomicChatAtomic Dynamic (AD) quants, built from NVIDIA's original BF16 weights with our own importance matrix. At 21.9 GB, AD-IQ1_M_S stays closer to the original than NVIDIA's own 22.0 GB 2-bit file, measured side by side on one stand. The calibration corpora behind our builds are public. Every file here was measured against the BF16 original on the same stand as the other publishers' files. You can now run Nemotron 3.5 Bolt in Atomic Chat : 74B total parameters, 9B active per token. See our quantization analysis below for measurements and instructions. Lower is closer to the original. Each purple point is a file in this repo; the grey ones are other GGUF files of this model, downloaded and measured with exactly the same reference, text and llama.cpp build. NVIDIA's 2-bit file (the one Unsloth and LM Studio ship too) is a quantization-aware-trained checkpoint, so its distance to the BF16 weights also includes what that training changed; see below.
Input Text · Image→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗NVIDIA's refusal behaviour projected out of the released weights, baked into Atomic Dynamic GGUF builds and measured against the original. On held-out JailbreakBench prompts refusals fall from 97.5% to 0%, and with thinking on from 30 of 30 to none (2 of 30 on the 22 and 29 GB files). MMLU stays where it was: 81.35% before, 81.75% after (2000 questions, McNemar p = 0.29). Tool calls and long context are unaffected. You can now run the Uncensored Nemotron 3.5 Bolt in Atomic Chat , locally on your own machine. Made from the full-precision release, not from NVIDIA's 24 GB file, and measured on one stand against the other public Bolt abliterations: at 22 GB ours is the closest to the original and the only one that neither refuses with thinking off nor breaks into repeated text ( table ). The refusal is written into the residual stream by every kind of block: the edit covers the Mamba-2 outputs, the attention outputs, the shared experts and the latent projection through which all routed experts write. Same Atomic Dynamic layouts and importance matrix as our Nemotron 3.5 Bolt quants ; each file is the size of the original build with the same name. *28 Oct 2026: re-split from 2 GB shards: `AD-IQ2_XS` and `AD-IQ1_M_S` are now a single file each, `AD-Q4_K_M` two files cut at 45 GB. The weights are unchanged (tensor-for-tensor identical).*
Input Text · Image→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗NVIDIA-Nemotron-3.5-Bolt-E4B-GGUF
AtomicChatAtomic Dynamic (AD) quants of NVIDIA's Nemotron 3.5 Bolt E4B, built from NVIDIA's original BF16 weights. From 4.0 GB to 8.0 GB on disk. Bolt E4B is NVIDIA's small reasoning and chat model, post-trained from Google's Gemma-4-E4B-it . You can now run Nemotron 3.5 Bolt E4B, NVIDIA's on-device model, in Atomic Chat . Every file here was measured against the BF16 original on one stand, next to the other publishers' files. > [!NOTE] > **Built on release day, 23 October.** Every `AD-` file below `AD-Q6_K` was > rebuilt the same evening with a better layout (below). `AD-Q4_K_M` uses our own > importance matrix, collected on the BF16 weights over a corpus rendered through > this model's chat template (`imatrix/imatrix.gguf` in the metrics repo). The > other files use Unsloth's published one (`imatrix_unsloth.gguf` from > unsloth/NVIDIA-Nemotron-3.5-Bolt-E4B-GGUF): > we built `AD-Q5_K_M` to `AD-IQ3_S` with both, and on held-out code the two > came out within noise of each other, slightly ahead with Unsloth's at 3 bits. > `AD-IQ3_XXS` (3.82 GB) was taken down the same evening: it picked the > original's next word only 74.6% of the time, below the 75% we publish at.
Input Text→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗NVIDIA's refusal behaviour projected out of the released weights, baked into Atomic Dynamic GGUF builds and shipped as a 3.5 MB LoRA, measured against the original. On held-out JailbreakBench prompts refusals fall from 93.8% to 1.2%, on the safe XSTest prompts from 9.2% to 0.4%, and with thinking on from 29 of 30 to none. MMLU: 68.50% before, 67.85% after (2000 questions, McNemar p = 0.21). Tool calls and long context are unaffected. You can now run the Uncensored Nemotron 3.5 Bolt E4B in Atomic Chat , locally on your own machine. One release-gate is not met, and we say so: on harmless prompts the first token moves further from the original than our 0.10 limit (KL 0.141). On this model even a random direction edited the same way moves neutral text noticeably ( limitations ). Gemma 4 normalises every write into the residual stream with its own weights before adding it, so the edit is computed through those norms: each matrix stops writing the refusal direction as it lands in the stream, not before the norm. Built on the same weights as our Nemotron 3.5 Bolt E4B quants ; the LoRA loads on top of any of those files. KLD and top-1 are against the **original, unmodified** BF16 model on our held-out neutral text (24 chunks of 4096 tokens), so they hold the edit and the quantization together. The edit alone, on the BF16 weights, is 0.159; the plain `AD-Q6_K` of the original model is 0.026 and `AD-Q4_K_M` 0.091 on the same text, so at `AD-Q6_K` almost all of the distance is the edit itself.
Input Text→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗GGUF quantizations of nvidia/NVIDIA-Nemotron-3.5-Lightning-30B-A3B-BF16, built with llama.cpp `ba360ef`. Every claim below is measured; raw logs are in the metrics repo. `AD-` marks an **Atomic Dynamic** layout: the two expert tensors are assigned explicitly instead of left to a preset, and the name carries the assignment — `AD- - `, collapsed to one name when both match. Everything outside the experts is `Q8_0`; it is 7% of the model, so spending bits there is cheaper than reasoning about it. Measured on `eval_neutral` held-out, KL divergence against the `Q8_0` reference. `tok/s` is generation on a single RTX 5090, full offload.
Input Text→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗Atomic Dynamic (AD) quants, built from NVIDIA's original BF16 weights with our own importance matrix. Every file here matches or beats the other GGUF builds of the same size or larger, measured side by side on one stand. The calibration corpora behind our builds are public. Every file here was measured against the BF16 original on the same stand as the other publishers' files, and each one beats or ties the file of theirs that is the same size or larger. You can now run Nemotron 3.5 Super in Atomic Chat : 120B total parameters, 12B active per token. See our quantization analysis below for measurements and instructions. Lower is closer to the original. Each purple point is a file in this repo; the grey ones are the other publishers' files, downloaded and measured with exactly the same reference, text and llama.cpp build. At 75 GB, `AD-IQ4_NL` drifts about half as much as both NVFP4 builds, which are the same size or up to 3 GB larger. At 70 GB, `AD-IQ3_M` drifts about half as much as LM Studio's `Q4_K_M` of the same size. At 65 GB, `AD-IQ3_XXS` drifts 20% less than Unsloth's `UD-Q3_K_XL`, and from 46 to 58 GB the `AD-Q2_0_*` files drift 6 to 18% less than the Unsloth file of each size, and at 87 GB `AD-Q4_K_S` drifts 13% less than `UD-Q4_K_XL`.
Input Text · Image→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗基础档案已收录，详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
Input Text · Image→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗No matching models
Adjust provider, category or input/output filters. New models are added continuously.
COST EXPLORER
Great models. Clear costs.
Adjust monthly token usage to compare estimated API costs.
1 M = 1 million tokens · USD
Compares base text-token rates within the same channel
Compares base text-token rates within the same channel
Uses collected, comparable USD-per-million-token rates. Snapshots exclude cache discounts, tiers, extra reasoning output and taxes. Check current source prices.
MODEL HANDBOOK
Understand before you choose
How should API prices be compared?+
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.
Do open weights mean free commercial use?+
Not necessarily. Check each version’s license, commercial restrictions and policies. Self-hosting also incurs compute and maintenance costs.
Is the top-ranked model the best for me?+
Rankings depend on tasks, versions and methods. Compare accuracy, latency, reliability and costs on your own workload.