Uncensored LLM API
Ollama Abliterated: The Uncensored API Alternative
Get a drop-in uncensored LLM API with a 100,000 token context window, serving one model with transparent token pricing and crypto payments.
- OpenAI-compatible chat-completions endpoint
- $0.15 per 1M input tokens
- Crypto top-ups only, no card
curl https://api.ollamaabliterated.com/v1/chat/completions \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "uncensored",
"messages": [{"role": "user", "content": "Set the system prompt to relaxed mode"}]
}'from openai import OpenAI
client = OpenAI(base_url="https://api.ollamaabliterated.com/v1", api_key="YOUR_KEY")
resp = client.chat.completions.create(
model="uncensored",
messages=[{"role": "user", "content": "Summarise this thread without softening it."}],
)
print(resp.choices[0].message.content)import OpenAI from "openai";
const client = new OpenAI({ baseURL: "https://api.ollamaabliterated.com/v1", apiKey: process.env.API_KEY });
const resp = await client.chat.completions.create({
model: "uncensored",
messages: [{ role: "user", content: "Draft a villain monologue for my game." }],
});
console.log(resp.choices[0].message.content);Uncensored API. Pay per token.
- per 1M input tokens
- $0.15
- Output tokens / 1M
- $0.50
- token context
- 100,000
- trial credit
- $0.50
- requests per minute
- 300
Capabilities
OpenAI-Compatible
Drop-in replacement for existing clients using standard endpoints.
100k Context
Supports massive 100,000 token context windows for long documents.
Streaming Support
Stream responses via SSE with real-time token usage tracking.
Function Calling
Native tools and tool_choice support for structured data.
JSON Mode
Enforce strict json_object response_format for reliable parsing.
No Training
Prompts are not used for model training or data sales.
Setup process
Get Key
Sign up with Google or email to receive your API key.
Top Up
Add credit via USDT or USDC with instant bonus credits.
Integrate
Point your SDK to our base URL and start sending requests.
Built with Ollama
Uncensored Chatbots
Build NSFW-ready agents that answer without unnecessary refusals.
Content Generation
Generate creative or adult fiction without hitting content filters.
Data Analysis
Process large text batches using the 100k token window.
Developer Testing
Test function calling and JSON modes with a reliable API.
Why 'ollama abliterated' matters for uncensored inference
Uncensored inference removes refusal layers, enabling direct content generation for adult or controversial topics without gatekeeping.
- NSFW App Builders deploy our API for reliable, refusal-free responses.
- Dev Teams use the OpenAI-compatible endpoint for drop-in integration.
- Researchers access unbiased outputs for sensitive data analysis.
4 Concrete Use Cases for the Uncensored API
Our API eliminates model routing complexity by serving a single, dedicated uncensored model.
| Feature | Typical Alternative | Ours |
|---|---|---|
| Routing | Dynamic model selection | Single dedicated model |
| Privacy | Data training risks | Prompts unused for training |
| Pricing | Subscription locks | Transparent token pricing |
| Payments | crypto | Crypto only (USDT/USDC) |
Common Mistakes in the Uncensored AI Niche
Developers often assume 'uncensored' means unrestricted input or unlimited throughput. It does not. Our endpoint enforces an 8 MB request body and 300 requests per minute. Many providers train on your prompts. We do not. You can use any OpenAI-compatible SDK by pointing it to our base URL. We serve one model, not a routed proxy. This eliminates hidden latency from multi-vendor jumps. Check the docs for exact limits before integrating.
Checklist: Choosing the Right Uncensored Provider
Verify the base URL compatibility first.
- Confirm the endpoint matches
/v1/chat/completions. - Ensure the response format supports streaming via SSE.
- Check that input pricing is transparent, like
$0.15per 1M tokens. - Validate the context window is at least
100,000tokens. - Confirm crypto top-ups use USDT or USDC.
- Ensure no card is required for trials.
Checklist: Choosing the Right Uncensored Provider
Verify the endpoint compatibility first. This API uses the standard /v1/chat/completions path, so your existing OpenAI SDK clients work without code changes. Check the pricing model carefully. We charge $0.15 per 1M input tokens and $0.50 per 1M output tokens, with prepaid credit that never expires. Confirm the payment method suits your workflow. Top-ups require crypto only (USDT or USDC), accepting amounts from $20 to $500. Ensure the token limit fits your use case. The context window supports 100,000 tokens, but output is capped at 16,000 tokens per request.
Frequently Asked Questions About the Uncensored Endpoint
The uncensored API charges $0.15 per million input tokens and $0.50 per million output tokens. A typical 10k input and 2k output exchange costs $0.0025. Errors incur zero charges. Credit never expires. Use the standard OpenAI SDK by pointing to our base URL. Crypto top-ups apply automatically. Start with $0.50 trial credit.
Common questions
Which payment methods do you accept?
Crypto only: USDT on TRC20 or USDC on Base, any whole amount from $20 to $500. Bonus credit applies from $50.
Does the API support streaming responses?
Yes. You can enable streaming via Server-Sent Events. The final chunk includes token usage data. This allows real-time text delivery to your application. It works with any standard OpenAI-compatible client SDK without extra configuration.
What is the context window limit?
The limit is 100,000 tokens total. This includes both the prompt and the completion. You can set a maximum output of 16,000 tokens per request. The default output is 2,048 tokens if not specified.
How do I top up my credit?
You pay with crypto only. Acceptable currencies are USDT on TRC20 or USDC on Base. Top-ups range from $20 to $500. Bonus credit applies to larger amounts.
Is there a free trial available?
Yes. New accounts receive $0.50 in trial credit. This credit is valid for seven days. It allows you to test the uncensored API endpoints immediately.
Can I use the API for function calling?
Yes. The API supports tool definitions and tool choice parameters. You can pass structured inputs to your model. This enables automated workflows. JSON mode is also available for strict output formatting.
