Developer quickstart for uncensored LLM
Drop an uncensored LLM into your existing stack with a single OpenAI-compatible API call. No model routing, no hidden subscriptions, just raw text generation.
- base_url
- https://api.chatbotunfiltered.com/v1
- model
- uncensored
Base URL and Authentication
Start by pointing your client to our base URL. We host a single uncensored large language model at https://api.chatbotunfiltered.com/v1. This endpoint replaces the standard OpenAI address, ensuring your existing code works without modification. Generate an API key via the dashboard using Google or email, then set it in your headers. We do not offer embeddings or image generation, only text completion.
Chat Completions Endpoint
Send your first request to POST /v1/chat/completions. Use the model ID uncensored to access the unfiltered model. This endpoint accepts standard message arrays and returns generated text. You can verify connectivity by listing models via GET. Keep your payload under 8 MB to avoid truncation.
curl https://api.chatbotunfiltered.com/v1/chat/completions \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "uncensored",
"messages": [{"role": "user", "content": "What is the capital of France?"}]
}'
Python SDK Integration
Configure the official Python SDK to target our base URL. Pass your API key as a header or environment variable. Set the model name to uncensored for consistent results. The SDK handles serialization automatically. Use this setup for quick scripts or complex role-play logic.
from openai import OpenAI
client = OpenAI(base_url="https://api.chatbotunfiltered.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 SDK Configuration
Initialize the Node client with our specific base URL. This ensures your JavaScript applications route requests correctly. The uncensored model ID remains constant across all SDKs. Configure the API key in your environment variables for secure access. This approach works seamlessly with Express or serverless functions.
import OpenAI from "openai";
const client = new OpenAI({ baseURL: "https://api.chatbotunfiltered.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 Responses with SSE
Enable streaming by setting stream: true in your request. We return Server-Sent Events (SSE) for real-time token delivery. The final chunk includes the complete token usage statistics. This method reduces perceived latency for long conversations. Handle the stream events in your client-side code.
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)
Rate Limits and Concurrency
Expect a limit of 300 requests per minute per key. You can run up to 8 concurrent requests simultaneously. If you exceed these bounds, you receive a 429 status code. Authentication failures return 401, and insufficient credit returns 402. The context window supports 100,000 tokens total. Errors during generation do not consume your prepaid credit.
Frequently asked questions
How do I start with an unfiltered chatbot API?
Sign up via Google or email to get an API key instantly. Add $20 in crypto to your account to begin sending requests. Use the base URL provided in your dashboard for all SDK integrations.
What are the rate limits for this uncensored LLM?
You are allowed 300 requests per minute with a concurrency limit of 8 requests. The context window supports up to 100,000 tokens. Exceeding these limits triggers a 429 error response.
Does this API support streaming responses?
Yes, you can enable streaming by setting the stream parameter to true. We return Server-Sent Events (SSE) for real-time token delivery. The final chunk includes the total token usage for billing purposes.
Get your API key instantly
Register, copy your key, update your base URL. Setup is complete.