Agens-Volundr-32B-v1
Blockway基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
기본 정보 등록 · 상세 정보 보완 예정
언어부터 이미지, 오픈 웨이트부터 API까지. 기능과 실제 비용을 비교하세요.
다음 아이디어에 맞는 AI를 찾아보세요.
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
기본 정보 등록 · 상세 정보 보완 예정
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
기본 정보 등록 · 상세 정보 보완 예정
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
기본 정보 등록 · 상세 정보 보완 예정
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
기본 정보 등록 · 상세 정보 보완 예정
Refusal removed from GLM-5.3-Flash by editing **666 of its 12,384 routed experts** — about **1.74% of the model's parameters**. Quantized to IQ1_S at **71.5 GiB**, which fits on a single 96 GB card. I did the edit and the quantization myself, and I measured what it cost. Every number below is first-party, taken on my own rig, on the file in this repo. > **Read this before you run it.** Every headline number below was measured at > **temperature 0, seed 0, repetition penalty 1.1/256, 16k context, `--reasoning-budget 1024`.** > The file itself ships `temperature 1.0` in its metadata and no reasoning budget, so a plain > `llama-server -m …` does **not** run the measured configuration. I tested that gap directly > (table under *Default settings vs tested settings*): at the file's own defaults, long coding > tasks ran out of output budget without answering about **1 time in 8**; with > `--reasoning-budget 1024` they did not. **For code and chat, use the quickstart line as > written. For hard math, leave the budget off** (see the correction below). This is an experimental 1.92-bit build: 37 of > 120 harmful-set responses and 8 of 120 benign ones hit the output cap in the headline run, and > that is reported separately from "unusable" below.
번역 대기 중 · 원문 표시
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
기본 정보 등록 · 상세 정보 보완 예정
An uncensored edit of **NVIDIA Nemotron-3.5-Bolt-74B-A9B**, a hybrid Mamba/MoE model, produced by editing NVIDIA's **shipped 24GB 2-bit GGUF** (nvidia/NVIDIA-Nemotron-3.5-Bolt-74B-A9B-24GB-GGUF) **directly** — no BF16 requantize at any point. That matters for this model specifically. Bolt is a LatentMoE: every routed expert sums through one dense `ffn_latent_up` per layer, and the experts themselves are ~17GB of IQ2_XXS weights produced by NVIDIA's quantization-aware distillation. A conventional abliterate-then-requantize pipeline would throw that QAD work away. Instead the projection is applied in place and codes are re-picked under the **original block scales**, so at λ=0 the output file is byte-identical to the input by construction — which is the self-test the build gates on (verified: all edited tensors byte-identical at λ=0). The published file is the same length as NVIDIA's, 22,018,326,528 bytes. Bolt is multimodal, so the projector ships alongside. The edit touched only text-model tensors, so the projector is byte-for-byte NVIDIA's file; download both or vision silently does nothing.
번역 대기 중 · 원문 표시
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
기본 정보 등록 · 상세 정보 보완 예정
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
기본 정보 등록 · 상세 정보 보완 예정
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
기본 정보 등록 · 상세 정보 보완 예정
GGUF conversion of internlm/Intern-Decision-4B, a multimodal structured-decision model fine-tuned from Qwen3.5-4B. The initial language-model conversions declared 33 transformer blocks while containing 32 tensor blocks. The uploaded FP16 and Q8_0 models correct the conversion metadata to `block_count=32`, `nextn_predict_layers=0`, and 32 recurrent-layer entries. Model tensors are unchanged. This correction is required by current llama.cpp builds. Intern-Decision is a candidate-scoring model rather than a general chat model. Follow the upstream model card's decision-schema prompt format, constrain each field to its allowed single-token answer symbols, and read the candidate probabilities. The upstream calibration temperature is `1.99241824`; it was fitted on BF16 weights, so Q8_0 quantization can change calibration quality.
번역 대기 중 · 원문 표시
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
기본 정보 등록 · 상세 정보 보완 예정
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
기본 정보 등록 · 상세 정보 보완 예정
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
기본 정보 등록 · 상세 정보 보완 예정
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
**We recommend `ThinkingCap-gemma-4-26B-A4B-it-MXFP4_MOE.gguf` over `Q4_K_M` at this size**: it is the file evaluated below, and it held up better on our math benchmarks. Pull it with `-hf bottlecapai/ThinkingCap-gemma-4-26B-A4B-it-GGUF:MXFP4_MOE`. GGUF / llama.cpp quantizations of bottlecapai/ThinkingCap-gemma-4-26B-A4B-it — ThinkingCap's shorter-thinking post-training applied to gemma-4-26B-A4B-it, a mixture-of-experts model with image input. ➡️ Full model description, evaluation results, the measured thinking-token reduction and recommended sampling: see the main model card at bottlecapai/ThinkingCap-gemma-4-26B-A4B-it.
번역 대기 중 · 원문 표시
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
기본 정보 등록 · 상세 정보 보완 예정
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
A **14.3 GB** GGUF of bottlecapai/ThinkingCap-Qwen3.8-27B that runs on an **18 GB GPU with image input, MTP speculative decoding and a 32k-token context all on the card**, and matched the bf16 weights on all five benchmarks we evaluated (2,863 questions: 81.00% against 81.03%). The standard GGUFs (ThinkingCap-Qwen3.8-27B-GGUF) start at IQ4_XS, 15.5 GB, which with the vision projector and a 32k context does not fit 18 GB. Every weight tensor was quantized with llama.cpp's own types (IQ2_S up to Q8_0, all with one importance matrix computed on the model's own reasoning traces). Which type each of the 401 language-model weight matrices gets was then picked by an RCO search: it minimizes the KL divergence between the bf16 model's and the mixed model's next-token distributions on 256 of the model's own traces, under an exact file-size budget. The same idea as ISTA-DASLab's GSQ-RCO GGUFs, searched on this finetune rather than the base model; the rounding itself is llama.cpp's.
번역 대기 중 · 원문 표시
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
제공사, 분류, 입출력 조건을 조정하세요. 새 모델이 계속 등록됩니다.
월간 토큰 사용량으로 예상 API 비용을 비교하세요.
수집된 백만 토큰당 USD 요금입니다. 캐시 할인, 구간 요금, 추가 추론 출력, 세금은 제외됩니다. 최신 요금은 출처에서 확인하세요.
입력, 출력, 캐시 요금을 구분하고 동일 작업량으로 비교하세요. 이미지, 음성, 영상은 개수, 시간, 해상도로 과금될 수 있습니다.
반드시 그렇지는 않습니다. 버전별 라이선스, 상업 이용 제한, 정책을 확인하세요. 자체 호스팅에는 연산 및 유지 비용도 듭니다.
순위는 작업, 버전, 평가 방식에 따라 다릅니다. 실제 업무로 정확도, 지연, 안정성, 비용을 비교하세요.