Abliterate
Explore Abliterate models on TrustedRouter with current routes, token pricing, policy sources, privacy posture, regional availability, and API support.
Abliterateabliterate
OpenAI-compatible chat and research models. When Abliterate omits usage, successful prepaid calls are billed using up to twice the locally estimated input and output tokens. The added buffer is limited by the authorized request budget and requested output limit. Responses mark usage_estimated=true. Provider-reported usage takes precedence. These are estimates, not verified upstream token counts.
These privacy labels describe Abliterate, the upstream model provider. Confidential requires all three: verified provider compute, end-to-end encryption and explicit zero data retention. Account and billing metadata are outside the content-retention claim.
| Provider | Abliterate |
|---|---|
| API operator country | Not verified Legal home of the API operator, not an inference-location guarantee. |
| Headquarters | Not verified |
| Routing status | Active |
| Provider website | https://abliterate.ai/ |
| Models | 3 public models |
| Credits routes | 3 |
| Zero data retention | not claimed |
| Verified confidential inference | Not verified |
| Policy note | Abliterate says prompts and completions are discarded after each request, but they transit an upstream inference provider whose retention is not identified in its terms. End-to-end ZDR and confidential inference are unverified. Policy source |
Documentation and policy sources
Inference locations
Provider API declarations are also available on each model's endpoint API. Direct chat and Responses replies separate advertised availability from serving location in usage.inference_location; the actual serving region remains unknown when not reported.
Where the upstream GPUs execute the model, not the provider's headquarters, API ingress, or data storage. ZDR and confidential inference do not by themselves restrict geography.
- Declared countries or regions
- Not verified
No inference-location declaration has been verified for this provider. - Can locations change?
- Not verified. Do not assume that the serving location is fixed.
- Provider region pinning
- Not verified.
- Pinning through TrustedRouter
- No verified provider-specific location pin documented here.
- Infrastructure declaration
- Inference location not verified; no country-specific residency commitment.
- Evidence
- Not yet reviewed.
Provider selection alone is not a region pin. TrustedRouter's US provider filter selects company jurisdiction, not GPU location. A regional gateway hostname does not pin a downstream GPU. For a binding residency requirement, confirm the model, region, failover scope and enforced controls before sending sensitive data.
Measured performance
34 samplesContinuously sampled across Abliterate's routed models: p50 TTFT, effective throughput, and success rate. Effective throughput uses provider-reported output tokens over complete request time. Unsupported route and probe-configuration rows are separated from provider downtime. No prompt or output content stored.
| p50 TTFT | 3327 ms |
|---|---|
| Effective throughput | — |
| Uptime | 85.29% |
| Model | p50 TTFT | Effective throughput | Uptime | Config excluded | Availability samples |
|---|---|---|---|---|---|
| abliterate/abliterate-0.3-fast | 1876 ms | — | 100.00% | — | 13 |
| abliterate/abliterate-0.3-balanced | 3327 ms | — | 100.00% | — | 12 |
| abliterate/abliterate-0.3-clever | 18746 ms | — | 44.44% | — | 9 |
Abliterate performance history · Full provider & model leaderboard.
Models served by Abliterate.
Each row links to pricing, provider, benchmark, and API pages for the model.
| Model | AI IQ | Context | Input | Cached input | Output |
|---|---|---|---|---|---|
abliterate/abliterate-0.3-balancedabliterate-0.3-balanced |
— | 0 | $0.9495/1M | Not published | $2.11/1M |
abliterate/abliterate-0.3-cleverabliterate-0.3-clever |
— | 0 | $2.6375/1M | Not published | $5.275/1M |
abliterate/abliterate-0.3-fastabliterate-0.3-fast |
— | 0 | $0.5275/1M | Not published | $1.055/1M |
Questions
Does Abliterate have zero data retention?
TrustedRouter does not currently mark Abliterate as provider-level zero data retention. Use trustedrouter/zdr or provider.min_privacy=zdr to select a different eligible route, and review the linked policy source for changes.
Is Abliterate end-to-end encrypted?
TrustedRouter does not currently mark Abliterate as end-to-end encrypted at the provider boundary. The TrustedRouter gateway is still attested, but the selected provider normally receives the request in order to run the model. Use trustedrouter/e2e for the stronger route requirement.
Which Abliterate models are available through TrustedRouter?
This page currently lists 3 public Abliterate models, with live pricing, route count, context length, measured performance when available, and links to each model's provider and benchmark pages.