API Documentation
Get your first uncensored response in under two minutes. This guide covers the OpenAI-compatible endpoint, authentication, and the exact parameters needed to bypass standard refusals.
Quickstart with the Official SDK
Start generating text immediately using your preferred language client. The API mirrors the standard chat completions interface, so you only need to swap the base URL and API key. This ensures your existing infrastructure works without rewriting logic.
curl https://api.abliteratedmeaning.com/v1/chat/completions \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "uncensored",
"messages": [{"role": "user", "content": "Return the definition of abliterated."}]
}'from openai import OpenAI
client = OpenAI(base_url="https://api.abliteratedmeaning.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.abliteratedmeaning.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);
Base URL and Authentication
Direct all requests to the dedicated base URL with your unique API key in the authorization header. This key is the only credential needed for every request to the /v1/chat/completions endpoint.
curl https://api.abliteratedmeaning.com/v1/chat/completions \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "uncensored",
"messages": [{"role": "user", "content": "Return the definition of abliterated."}]
}'
Chat Completions Endpoint
Send text data to receive raw text output from the uncensored model. Use the uncensored model ID to access the tuned version that skips typical corporate guardrails. The endpoint supports standard JSON payloads, including temperature, top_p, and stop sequences for precise control over the generation process.
from openai import OpenAI
client = OpenAI(base_url="https://api.abliteratedmeaning.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)
Streaming and Tool Usage
Enable real-time token delivery by setting the stream parameter to true in your request body. This returns Server-Sent Events (SSE) where the final chunk contains the total token usage for billing transparency. You can also define tools for function calling or force JSON output using the response_format parameter.
stream = client.chat.completions.create(
model="uncensored",
messages=[{"role": "user", "content": "Tell the story in second person."}],
stream=True,
)
for chunk in stream:
if chunk.choices and chunk.choices[0].delta.content:
print(chunk.choices[0].delta.content, end="", flush=True)
Parameters and Limits
Control the model behavior with standard parameters like temperature and seed, but respect the hard limits of the system. Each request can contain up to 100,000 tokens for the context window, with a maximum output of 16,000 tokens per call. If you do not specify max_tokens, the default output is capped at 2,048 tokens.
Frequently asked questions
What happens if my API key is invalid?
The server returns a 401 Unauthorized error immediately. Check that you copied the key correctly from your dashboard and that you are using the correct base URL. Regenerate your key if you suspect it was exposed.
Why do I get a 402 error?
This indicates your prepaid credit balance is zero or insufficient for the request. Credits never expire, so you can top up with USDT or USDC at any time. Errors and refusals do not consume credit, but successful completions do.
What are the rate limits for this uncensored LLM?
You are limited to 300 requests per minute and 8 concurrent requests per key. If you exceed these limits, you will receive a 429 Too Many Requests error. Wait a few seconds before retrying or upgrade your plan if you need higher throughput.
Secure your API key
Sign up, grab the key, update the base URL. Done.