nl ▾

API Quickstart

Get started with the uncensored LLM API in minutes. Use standard OpenAI SDKs to send requests to our single, abliterated model.

Base URL and Authentication

Our API accepts standard OpenAI-compatible requests via a single base URL. Point your client to https://api.abliteratedaimodels.com/v1 and include your key in the Authorization header. You generate this key instantly after signing up with Google or email. The system issues one active key per account; generating a new one revokes the previous key immediately.

  • Base URL: https://api.abliteratedaimodels.com/v1
  • Header: Authorization: Bearer YOUR_API_KEY
  • Model ID: uncensored

Basic Completion Request

Send a standard chat completion request to get text output. The model responds without filtering for lawful adult, controversial, or niche topics. Input tokens cost $0.15 per 1M, and output tokens cost $0.50 per 1M. Errors and refusals do not consume your prepaid credit.

Python SDK Integration

Use the official OpenAI Python package to interact with the endpoint. Set the base URL and API key in your client configuration. This allows you to leverage existing libraries built for OpenAI while accessing our uncensored model.

Node SDK Integration

Configure the OpenAI Node.js SDK to point to our base URL. Pass your API key and set the model to uncensored. This approach works with any OpenAI-compatible client library. You can adjust parameters like temperature and top_p to control output randomness.

Streaming Responses with SSE

Enable streaming by setting stream: true in your request. The API returns Server-Sent Events (SSE) as tokens are generated. This reduces perceived latency for chat applications. The final chunk includes the total token usage for the request.

Limits, Errors, and Context

The context window supports 100,000 tokens for prompt and completion combined. Max output is 16,000 tokens per request. Rate limits are 300 requests per minute and 8 concurrent requests per key. Handle errors appropriately: 401 indicates an invalid key, 402 means insufficient credit, and 429 signals rate limit exceeded. Requests over 8 MB are rejected.

cURL

curl https://api.abliteratedaimodels.com/v1/chat/completions \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "uncensored",
    "messages": [{"role": "user", "content": "Calculate the total bytes for a 1024 token sequence"}]
  }'

Python

from openai import OpenAI

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

import OpenAI from "openai";

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

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)

Frequently asked questions

How does abliterated AI models differ from other uncensored LLM options?

Our model has guardrails mathematically scrubbed from its weights, providing unrestricted outputs without degrading base intelligence. It is a single, dedicated model, not a routed proxy. This ensures consistent behavior and predictable pricing per token.

What happens if I exceed my rate limit?

The API returns a 429 status code. You can retry after the window resets or upgrade your credit volume. The limit is 300 requests per minute and 8 concurrent connections per key. Exceeding these limits does not incur extra charges.

Is the uncensored API truly openai compatible?

Yes, it uses the same <code>/v1/chat/completions</code> endpoint and request structure. You only need to change the base URL and API key. All standard parameters like <code>temperature</code>, <code>stop</code>, and <code>seed</code> work as expected.

Generate your API key

Register, retrieve your key, and point your base URL. That is the entire configuration.

Try with trial credit