API Documentation

Base URL and authentication

Point your client to https://api.obliterationai.com/v1 and include your key in the Authorization header. This base URL works with any OpenAI-compatible client by simply swapping the endpoint. You receive one active key per account, and generating a new one immediately invalidates the previous key. The service requires no phone number for signup, using only a Google login or email and password.

Authentication Header: Authorization: Bearer YOUR_API_KEY

Chat completions endpoint

Send messages to POST /v1/chat/completions to receive text responses from the uncensored model. The system accepts standard message formats and returns generated text without content refusals for lawful adult use. You must specify the model ID as "uncensored" in your request payload. This single endpoint handles all text generation needs, excluding embeddings or vision tasks.

Copycurl https://api.obliterationai.com/v1/chat/completions \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "uncensored",
    "messages": [{"role": "user", "content": "fetch me the latest release notes"}]
  }'

Python SDK integration

Use the official OpenAI Python library to interact with the API by updating the base URL. Set the api_key and base_url parameters to match our hosted endpoint. The client will route requests to the uncensored model using the specified model ID. This approach requires minimal code changes for existing OpenAI projects.

Copyfrom openai import OpenAI

client = OpenAI(base_url="https://api.obliterationai.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)

Node.js client setup

Initialize the OpenAI SDK in Node.js with the custom base URL and your API key. Configure the client to target the uncensored model ID for all completions. This setup allows you to leverage existing Node.js tools while accessing an unfiltered LLM. Ensure you pass the correct authentication headers for secure access.

Copyimport OpenAI from "openai";

const client = new OpenAI({ baseURL: "https://api.obliterationai.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);

Streaming and token usage

Enable streaming by setting stream: true to receive token-by-token responses via Server-Sent Events. The final chunk of the stream contains the total token usage for the request. This feature is ideal for real-time applications where latency matters. You can adjust parameters like temperature and top_p to control response variability.

Copystream = 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)

Rate limits and constraints

The API enforces a limit of 300 requests per minute and allows eight concurrent requests per key. The context window supports 100,000 tokens total, with a maximum output of 16,000 tokens per request. Errors such as invalid keys (401) or insufficient credit (402) do not consume your prepaid balance. A 429 status indicates you have exceeded the rate limit temporarily.

Hard content limit: no sexual content involving minors is allowed under any circumstances.