AI NEWS · 模型情报站发现能力边界,让每一次选择更有依据 ↗基础档案先收录 · 缺失资料持续补齐
THE AI MODEL DIRECTORY 模型探索,从这里开始

找到适合你的 AI 模型。

从语言到影像,从开源到 API。读懂模型能力、比较真实成本,
为你的下一个想法,找到合适的智能引擎。

热门探索
84,991 款模型档案13202 家厂商 / 发布者45 个能力分类465 款有可比报价 · 30 款有公开评测
T文本生成▧图像生成▷视频生成⌘代码生成◖语音合成♫音乐生成⬡3D 建模▤文档分析
DISCOVER & COMPARE

探索 AI 模型 84991

为你发现值得关注的模型

This repository contains unofficial GGUF Quantizations of Grok-1, compatible with `llama.cpp` as of PR- Add grok-1 support #6204. - The splits have been updated to utilize the improvements from PR: llama_model_loader: support multiple split/shard GGUFs. As a result, manual merging with `gguf-split` is no longer required. With this, there is no need to merge the split files before use. Just download all splits and run llama.cpp with the first split like you would previously. It'll detect the other splits and load them as well.

译文排队中 · 当前显示来源原文

分类待补充
输入 待核验→ 输出 待核验
价格待核验多模态与渠道费用须分别核对
查看详情 ↗
来源 / 文档 ↗

17 GGUF files of LiquidAI/LFM2.5-2.6B at the sizes of bartowski's quants and LiquidAI's own, with 26–77 % less KL divergence than the published file of the same size (about half or less from 3 to 5 bits per weight). Two things make the difference: **Build your own size:** the qalloc app solves the mix for any size you pick and assembles the GGUF in your browser, tensor by tensor from the store. Per token, against the BF16 model: the mean KL divergence and its 99th percentile (lower is better), and how often the most likely next token is the BF16 model's (higher is better), for the published file of the same size → this file. Where two published files are within 1 % of each other's size, one file here serves both.

译文排队中 · 当前显示来源原文

输入 文本→ 输出 文本
价格待核验多模态与渠道费用须分别核对
查看详情 ↗
来源 / 文档 ↗

- `source/`: LiquidAI's BF16 GGUF (LiquidAI/LFM2.5-2.6B-GGUF), unchanged. - `types/ -hq.gguf`, `types/ -hq1.gguf`: the tensors at llama.cpp type `T`, rebuilt from the BF16 weights in two Hessian-quantized (GPTQ-family) builds: `-hq`, the higher-quality one, the block tensors; `-hq1`, the first build, every quantized tensor. Same type, format and size as llama.cpp's: plain GGUF types, for stock llama.cpp (a GGUF assembled from them holds the plain type `T`); modified versions of the original weights. - `data/`: the calibration data the types were made from (token ids and their manifest). - `manifest.json` (`qcore-store/1`), `skeleton.gguf`, `store.json`, `records/`: what qalloc reads, with every tensor's offset and sha256. The first version of this store (bartowski's BF16 GGUF and imatrix, types by llama.cpp's `llama-quantize`) is at revision `fe50613`.

译文排队中 · 当前显示来源原文

分类待补充
输入 待核验→ 输出 待核验
价格待核验多模态与渠道费用须分别核对
查看详情 ↗
来源 / 文档 ↗

基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。

基础资料已收录 · 缺失资料后续补充

分类待补充
输入 待核验→ 输出 待核验
价格待核验多模态与渠道费用须分别核对
查看详情 ↗
来源 / 文档 ↗

Qwen/Qwen3.5-4B quantized to 25 llama.cpp types, each tensor at each type, for assembling GGUFs with a type per tensor.

译文排队中 · 当前显示来源原文

分类待补充
输入 待核验→ 输出 待核验
价格待核验多模态与渠道费用须分别核对
查看详情 ↗
来源 / 文档 ↗

10 GGUF files of Qwen/Qwen3.8-27B at the sizes of Unsloth's dynamic quants and of ISTA-DASLab's GSQ-RCO quants, with 16–38 % less KL divergence than the Unsloth file of the same size and 11–26 % less than ISTA-DASLab's. Two things make the difference: **Build your own size:** the qalloc app solves the mix for any size you pick and assembles the GGUF in your browser, tensor by tensor from the store. Per token, against the BF16 model: the mean KL divergence and its 99th percentile (lower is better), and how often the most likely next token is the BF16 model's (higher is better), for the published file of the same size → this file.

译文排队中 · 当前显示来源原文

输入 文本→ 输出 文本
价格待核验多模态与渠道费用须分别核对
查看详情 ↗
来源 / 文档 ↗

- `source/`: Unsloth's BF16 GGUF (unsloth/Qwen3.8-27B-GGUF), unchanged. - `types/ -hq.gguf`: every linear block tensor at llama.cpp type `T` (IQ1_M … Q8_0, IQ4_NL, MXFP4, NVFP4), rebuilt from the BF16 weights Hessian-quantized. Same type, format and size as llama.cpp's: plain GGUF types, for stock llama.cpp (a GGUF assembled from them holds the plain type `T`); modified versions of the original weights. - `types/ .gguf` (Q2_K … Q8_0): token_embd, output, the multi-token-prediction layer and the linear attention's small `ssm_alpha` / `ssm_beta` tensors at llama.cpp's own quantization. - `manifest.json` (`qcore-store/1`), `skeleton.gguf`, `store.json`, `records/`: what qalloc reads, with every tensor's offset and sha256. The earlier version of this store (every tensor at ~41 types by llama.cpp's and ik_llama.cpp's quantizers) is at revision `0090490`.

译文排队中 · 当前显示来源原文

分类待补充
输入 待核验→ 输出 待核验
价格待核验多模态与渠道费用须分别核对
查看详情 ↗
来源 / 文档 ↗

基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。

基础资料已收录 · 缺失资料后续补充

输入 文本→ 输出 文本
价格待核验多模态与渠道费用须分别核对
查看详情 ↗
来源 / 文档 ↗

基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。

基础资料已收录 · 缺失资料后续补充

输入 文本→ 输出 文本
价格待核验多模态与渠道费用须分别核对
查看详情 ↗
来源 / 文档 ↗

基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。

基础资料已收录 · 缺失资料后续补充

输入 文本→ 输出 文本
价格待核验多模态与渠道费用须分别核对
查看详情 ↗
来源 / 文档 ↗

The easiest way to starting using `jina-embeddings-v2-base-en` is to use Jina AI's Embedding API. `jina-embeddings-v2-base-en` is an English, monolingual **embedding model** supporting **8192 sequence length**. It is based on a BERT architecture (JinaBERT) that supports the symmetric bidirectional variant of ALiBi to allow longer sequence length. The backbone `jina-bert-v2-base-en` is pretrained on the C4 dataset. The model is further trained on Jina AI's collection of more than 400 millions of sentence pairs and hard negatives. These pairs were obtained from various domains and were carefully selected through a thorough cleaning process. The embedding model was trained using 512 sequence length, but extrapolates to 8k sequence length (or even longer) thanks to ALiBi. This makes our model useful for a range of use cases, especially when processing long documents is needed, including long document retrieval, semantic textual similarity, text reranking, recommendation, RAG and LLM-based generative search, etc.

译文排队中 · 当前显示来源原文

输入 文本→ 输出 向量
价格待核验多模态与渠道费用须分别核对
查看详情 ↗
来源 / 文档 ↗
COST EXPLORER

好模型,也要算好成本。

费用分析

调整月度 Token 用量,直观比较不同模型的预估 API 开支。

1 M = 100 万 Token · 美元计价
仅比较同一渠道的基础文本 Token 报价

使用已采集且单位可比的 USD / 百万 Token 渠道报价。报价为采集时快照;不计缓存优惠、阶梯价、推理额外输出与税费,请以来源的当前报价为准。

MODEL HANDBOOK

读懂模型,再做选择

选型与常见问题
API 价格应该怎么比较?+

先区分输入、输出和缓存价格,再使用同一任务和用量估算总费用。图像、音频和视频可能按张、时长或分辨率计费,不能直接与 Token 单价比较。

开放权重,就代表可以免费商用吗?+

不一定。必须逐一核对具体模型版本的许可证、商用限制及使用政策。自己部署还需要考虑显存、推理资源和运维费用。

排行榜第一,就是最适合我的模型吗?+

榜单取决于测试任务、版本与评测方法。建议用实际业务样本比较准确性、时延、稳定性和成本,再选择模型。

AI NEWS · 从信息到选择

资讯看趋势,工具提效率,模型筑可能。

探索 AI 资讯 ↗发现 AI 工具 ↗