MODEL PROFILE

orcarouter_GLM-5.3-Flash-Uncensored-GGUF

BoldingBuilds · orcarouter_GLM-5.3-Flash-Uncensored-GGUF

GGUF quantizations of **orcarouter/GLM-5.3-Flash-Uncensored-FP8**, built with a custom importance matrix and measured rather than assumed. > ⚠️ **Uncensored model.** Safety refusals were removed by OrcaRouter. It will comply with > harmful, unethical, and illegal requests. Released for research — red-teaming, refusal- > mechanism study, robustness evaluation. You are responsible for what you do with it. > 🔧 **What happened, and where it stands (2026-09-06).** On 2026-09-05 a user reported > looping and incoherent output from `IQ2_S` (discussion #1). They were > right. The original build pinned only the `blk.45` MTP block at high precision; attention, > the **shared** experts, the three dense FFN blocks, and the embeddings were all quantized > down with the routed experts. The shared experts and attention run on every token. > > **`IQ2_S` was rebuilt on 2026-09-06** with those tensors held at `q8_0` (+7 GB) and tested > against the original on a rented H200: 12 tasks × 2 seeds × 2 samplers, same scorer, same > settings. Full table in **Coherence gate** below. Short version: the original failed 3 of 8 > coding tasks by reasoning to the output cap without ever answering; the rebuild passed > all 48, matching `IQ3_XXS`, which also passed all 48 on its original recipe. > **`IQ2_XXS` is being rebuilt the same way** and stays flagged until it passes the same gate. > > **Two corrections to earlier versions of this page.** The imatrix has **10 chunks, not 60** > (the run checkpointed at 10 and stopped; numerically sound, one uncovered expert row in > `blk.29`). And the repetition-penalty workaround I posted **did not change the outcome** on > this failure mode — 21/24 → 21/24 for the original file with and without it. It helps > n-gram repetition; it does not help a model that cannot emit the literal it intends. > The rebuilt files carry `repeat_penalty 1.1` in their metadata anyway, because it is cheap. > > Only `IQ3_XXS` had been benchmarked before publication, and I shipped all three off that. > That was the actual mistake. The gate below is the fix for the process, not just the file.

Text generationlicense:mit
Context windowNot disclosed
Input → OutputText → Text
Model weightsNot verified
Profile updated2026/10/28 21:28:05
OVERVIEW

Model overview

GGUF quantizations of **orcarouter/GLM-5.3-Flash-Uncensored-FP8**, built with a custom importance matrix and measured rather than assumed. > ⚠️ **Uncensored model.** Safety refusals were removed by OrcaRouter. It will comply with > harmful, unethical, and illegal requests. Released for research — red-teaming, refusal- > mechanism study, robustness evaluation. You are responsible for what you do with it. > 🔧 **What happened, and where it stands (2026-09-06).** On 2026-09-05 a user reported > looping and incoherent output from `IQ2_S` (discussion #1). They were > right. The original build pinned only the `blk.45` MTP block at high precision; attention, > the **shared** experts, the three dense FFN blocks, and the embeddings were all quantized > down with the routed experts. The shared experts and attention run on every token. > > **`IQ2_S` was rebuilt on 2026-09-06** with those tensors held at `q8_0` (+7 GB) and tested > against the original on a rented H200: 12 tasks × 2 seeds × 2 samplers, same scorer, same > settings. Full table in **Coherence gate** below. Short version: the original failed 3 of 8 > coding tasks by reasoning to the output cap without ever answering; the rebuild passed > all 48, matching `IQ3_XXS`, which also passed all 48 on its original recipe. > **`IQ2_XXS` is being rebuilt the same way** and stays flagged until it passes the same gate. > > **Two corrections to earlier versions of this page.** The imatrix has **10 chunks, not 60** > (the run checkpointed at 10 and stopped; numerically sound, one uncovered expert row in > `blk.29`). And the repetition-penalty workaround I posted **did not change the outcome** on > this failure mode — 21/24 → 21/24 for the original file with and without it. It helps > n-gram repetition; it does not help a model that cannot emit the literal it intends. > The rebuilt files carry `repeat_penalty 1.1` in their metadata anyway, because it is cheap. > > Only `IQ3_XXS` had been benchmarked before publication, and I shipped all three off that. > That was the actual mistake. The gate below is the fix for the process, not just the file.

Key features

特点摘要待依据来源补齐,不凭模型名称推断能力。

Limitations & considerations

Sources are insufficient to establish specific limitations. Verify task performance, latency, data policies, licensing and version lifecycle.

PRICING & COST

Source prices & cost analysis

Prices vary by channel, region and configuration. Channel quotes are listed independently and are not treated as a single official provider price.

Source / channelInputOutputBilling unitCollected at
No verified prices yet. Check the source channel.

Estimate monthly base token costs

—

Estimates exclude cache discounts, tiered pricing, multimodal surcharges, web search, taxes and additional reasoning output.

INDEPENDENT BENCHMARKS

Public benchmarks & run configuration

暂无已采集的可核验公开评分。模型未上榜不代表能力较低。

View full indexed rankings →

Frequently asked questions

Do open weights permit free commercial use?

Not necessarily. Check the version license, commercial conditions and usage policies. Self-hosting incurs compute and maintenance costs.

Are these real-time billing prices?

These are timestamped source snapshots, not live billing prices. Check the channel for current versions, regions, discounts and billing methods.

Sources & traceability

许可证:mit。模型介绍与第三方评测均以原来源的具体版本和方法为准。