基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
探索 AI 模型 84959
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
基础资料已收录 · 缺失资料后续补充
Nitro-1-SD
amd基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
Nitro-E
amd基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
基础资料已收录 · 缺失资料后续补充
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
基础资料已收录 · 缺失资料后续补充
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
基础资料已收录 · 缺失资料后续补充
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
tiny-llama-fast-tokenizer
amd-quark基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
基础资料已收录 · 缺失资料后续补充
tiny-random-qwen3_moe
amd-quark基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
基础资料已收录 · 缺失资料后续补充
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
基础资料已收录 · 缺失资料后续补充
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
基础资料已收录 · 缺失资料后续补充
The model was quantized from Qwen/Qwen3.5-397B-A17B-FP8 using AMD-Quark. The weights are quantized to MXFP4 and activations are quantized to MXFP4. For further details or issues, please refer to the AMD-Quark documentation or contact the respective developers. The GSM8K results were obtained using the vLLM framework, based on the Docker image `rocm/vllm-dev:nightly_main_20260211`, and vLLM is installed inside the container.
译文排队中 · 当前显示来源原文
This checkpoint extends the routed-expert MXFP4 quantization by **also quantizing the shared expert to MXFP4 and fusing it into the routed MoE kernel** (FSE: fused shared expert). Compared with keeping the shared expert in bf16, this further reduces the bf16 footprint and improves decode throughput, with no measurable accuracy loss on GSM8K (see Evaluation). The model was quantized from Qwen/Qwen3.5-397B-A17B using AMD-Quark. Weights and activations are quantized to OCP MXFP4. For further details or issues, please refer to the AMD-Quark documentation or contact the respective developers.
译文排队中 · 当前显示来源原文
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
基础资料已收录 · 缺失资料后续补充
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
基础资料已收录 · 缺失资料后续补充
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
基础资料已收录 · 缺失资料后续补充
- **Model Architecture:** Qwen3_5MoeForCausalLM - **Input:** Text - **Output:** Text - **Supported Hardware Microarchitecture:** AMD MI350 / MI355 - **ROCm**: 7.2.0 - **PyTorch**: 2.12.0 - **Transformers**: 5.14.1 - **Operating System(s):** Linux - **Inference Engine:** SGLang/vLLM - **Model Optimizer:** AMD-Quark (v0.12) - **Quantized layers:** router experts - **Weight quantization:** OCP MXFP4, Static - **Activation quantization:** OCP MXFP4, Dynamic The model was quantized from Qwen/Qwen3.8-2.4T-A95B-FP8 using AMD-Quark. The weights and activations of the routed experts are quantized to MXFP4. For further details or issues, please refer to the AMD-Quark documentation or contact the respective developers.
译文排队中 · 当前显示来源原文
INT4 weight-only (W4A16) quantized version of `Qwen/Qwen3.8-27B`, produced with the **AWQ** algorithm using AMD Quark. \* BFCL Overall Acc reflects only `single_turn` categories, not the full Gorilla-leaderboard formula (multi-turn/web-search/memory categories were not run and would count as 0 against the public leaderboard's own Overall Acc). Sub-metrics: Non-Live AST 86.58% (base 88.52%), Live AST 81.57% (base 83.05%), Relevance Detection 75.00% (base 75.00%), Irrelevance Detection 72.47% (base 72.22%). Recovery % = quantized / BF16-base, using flexible-extract for GSM8K rows and base/quantized (inverted, since lower is better) for perplexity — both measured by us against verified-upstream `Qwen/Qwen3.8-27B` weights, not vendor-reported numbers. GSM8K uses `lm-evaluation-harness`; non-thinking mode is approximated by pre-closing an empty ` ` block in the prompt, since the harness task is a raw few-shot completion rather than a chat-templated request. BFCL run via the official `bfcl_eval` harness.
译文排队中 · 当前显示来源原文
- **Weights:** MXFP4 (OCP microscaling FP4, group size 32, E8M0 shared scale) - **Activations:** MXFP4, dynamic (per-block, computed at runtime) - **Algorithm:** AWQ - **Calibration:** 128 samples, seq_len 512, `pileval` dataset (Quark default) - **Base model:** Qwen/Qwen3.8-27B (bf16) - **Vision tower:** left unquantized (bf16) — only the language-model decoder (`model.language_model.layers`) is quantized; `model.visual.*` is excluded Recovery % is computed on the flexible-extract metric (`this model / bf16 base`). Non-thinking mode: the raw-completions endpoint used above doesn't support passing `enable_thinking=False` through a chat template, so non-thinking mode is approximated with a custom task that pre-closes an empty ` ` block in the prompt:
译文排队中 · 当前显示来源原文
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
基础资料已收录 · 缺失资料后续补充
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
基础资料已收录 · 缺失资料后续补充
暂未找到匹配模型
可以调整厂商、分类或输入输出条件;新模型正持续收录。
好模型,也要算好成本。
调整月度 Token 用量,直观比较不同模型的预估 API 开支。
仅比较同一渠道的基础文本 Token 报价
使用已采集且单位可比的 USD / 百万 Token 渠道报价。报价为采集时快照;不计缓存优惠、阶梯价、推理额外输出与税费,请以来源的当前报价为准。
读懂模型,再做选择
API 价格应该怎么比较?+
先区分输入、输出和缓存价格,再使用同一任务和用量估算总费用。图像、音频和视频可能按张、时长或分辨率计费,不能直接与 Token 单价比较。
开放权重,就代表可以免费商用吗?+
不一定。必须逐一核对具体模型版本的许可证、商用限制及使用政策。自己部署还需要考虑显存、推理资源和运维费用。
排行榜第一,就是最适合我的模型吗?+
榜单取决于测试任务、版本与评测方法。建议用实际业务样本比较准确性、时延、稳定性和成本,再选择模型。