Uncensored vs Abliterated AI Models: Differences & API IDs

What is the difference?

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.

Which should you choose?

Choose an uncensored model for a reduced-refusal instruction profile. Choose an abliterated model for weight-level refusal reduction. Compare each variant on your prompts, required output format and cost per successful result.

RouterHub’s prompt-profile uncensored variants use a server-managed instruction profile. Customer system/developer instructions can be replaced by that profile; put task-specific requirements in the user message.

Uncensored and abliterated API IDs

Compare cost per successful task

For ordinary uncached text usage, estimate cost as input tokens × input price / 1,000,000 + output tokens × output price / 1,000,000. Reported cache reads and writes use their own published rates. The final Usage record, not time spent waiting or a headline token limit, is the billing reference.

Example: at $0.20 per million input tokens and $0.60 per million output tokens, 10,000 uncached input tokens and 2,000 output tokens cost an estimated $0.0032. This is an illustrative calculation, not a quoted price for a particular model.

For model selection, divide the total cost of all measured attempts by the number of acceptable results. A lower token rate is not automatically a lower cost per completed task.

Test refusal behavior and quality separately

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.

RouterHub’s public coding evaluations on GitHub include prompts, raw outputs, settings, candidate hashes and sandbox-scored tests. The GLM results record both the default-effort attempts and the low-effort cohort, so you can compare runs with their original settings.

Next steps

• Use an uncensored model through an APIConnect with Python or cURL.
• How abliteration worksUnderstand weight-level refusal reduction.
• RouterHub comparison repositoryRead the source, examples and project notes on GitHub.