What does abliterated mean?

Uncensored models are reduced-refusal language model variants for open-ended generation, coding and creative work. Uncensored variants use prompting, fine-tuning, weight changes, or a combination of these techniques.

Abliteration reduces refusal-related behavior by modifying model weights. RouterHub serves uncensored and abliterated variants under separate API IDs, with their own token prices and context limits.

How does abliteration differ from prompting?

A system prompt changes the instructions a model receives at inference time. Fine-tuning trains weights on additional examples. Abliteration targets representations associated with refusal and modifies model weights to reduce their effect.

With a hosted abliterated API, RouterHub handles model serving. Select the model ID, connect with your API key and send requests from your application. With local inference, download the checkpoint and configure the runtime on your own hardware.

Compare generation quality

Evaluate factual accuracy, writing style, code correctness, tool calls, context handling and instruction following. Use the same prompts and token budgets to compare a standard model with its abliterated sibling.

Abliterated model API entries

RouterHub token prices · USD per million tokens
Model / exact API IDVariantInputCached inputOutputContextAvailability
GLM 5.3 Flash Abliterated
glm-5.3-flash-abliterated
abliterated$0.3$0.12$11,048,576 tokenspreview
GLM 5.3 Abliterated
glm-5.3-abliterated
abliterated$0.4$0.16$1.3333333333331,048,576 tokenspreview
DeepSeek V4.1 Flash Abliterated
deepseek-v4.1-flash-abliterated
abliterated$0.3$0.055$1.251,000,000 tokenspreview
DeepSeek V4 Pro Abliterated
deepseek-v4-pro-abliterated
abliterated$0.4$0.04$1.61,000,000 tokenspreview
DeepSeek V4.1 Flash 1017 Abliterated
deepseek-v4.1-flash-1017-abliterated
abliterated$0.3$0.055$1.251,000,000 tokenspreview

Evaluate your model

  1. Fix the task. Use the same inputs, output format, reasoning setting and output budget for each exact model ID.
  2. Separate refusal from failure. Record an explicit refusal separately from a timeout, empty response, invalid JSON, wrong answer or truncated generation.
  3. Keep every attempt. Repeat your tests and retain unsuccessful outputs, not just the best answer.
  4. Measure useful work. Compare task acceptance, instruction following, tool-call validity and cost per successful task, not token price alone.
  5. Re-test changes. A hosted alias or model update can change behavior even when your client configuration stays the same.