API Documentation & Quickstart

Authentication & Base URL

Start by generating your API key on the dashboard. We use standard OpenAI-compatible headers, so you only need to update your base_url and API_KEY variables. This ensures your existing SDK integrations work without modification. We support Google Sign-In or email/password registration, and your key appears immediately upon creation.

• Base URL: https://api.routeropen.cc/v1
• Auth Header: Authorization: Bearer YOUR_API_KEY

Keep your key secure, as it controls your prepaid credit. Each account allows one active key at a time; generating a new one replaces the old immediately.

First Request

Send your first prompt using the standard chat/completions endpoint. The model ID is simply uncensored. This sends text in and returns text out, with no content filters for lawful adult use.

Copycurl https://api.routeropen.cc/v1/chat/completions \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "uncensored",
    "messages": [{"role": "user", "content": "list all files in current directory"}]
  }'

This request demonstrates the basic structure. You can adjust parameters like temperature or top_p to control creativity. The response includes token usage stats for transparent billing.

Python SDK Integration

Use the official OpenAI Python library to integrate our API. Point the client to our base URL and use your API key. This approach works seamlessly with existing codebases that already target OpenAI.

Copyfrom openai import OpenAI

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

The library handles JSON serialization and streaming automatically. You can configure retry logic and timeouts as needed. Our endpoint supports standard parameters, making migration from other providers trivial.

Node SDK Integration

For JavaScript developers, the Node SDK works with minimal changes. Set the baseURL to our endpoint and provide your key. This allows you to maintain your current development workflow while accessing uncensored models.

Copyimport OpenAI from "openai";

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

Node users can leverage async/await patterns for clean code. The response structure matches OpenAI standards, ensuring compatibility with existing parsers. You can switch models or providers by changing just two variables.

Streaming Responses

Enable streaming by setting stream: true in your request. We return Server-Sent Events (SSE) for real-time token delivery. This reduces perceived latency for end-users.

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)

The final chunk contains the total token usage for billing. Streaming works with all parameters, including function calling. Use this for chat interfaces where instant feedback is critical. Errors are still returned as SSE events, so you can handle failures gracefully.

Limits, Errors & Context

Our API enforces a 100,000-token context window and an 8MB request body limit. You can make 300 requests per minute per key. If you exceed this, you receive a 429 rate limit error. Authentication failures return 401, and insufficient credits return 402.

Errors do not consume your prepaid credit. If you send a malformed request, you are not charged. The model refuses requests involving minors, but otherwise allows unrestricted content. Keep your error handling robust to manage rate limits effectively.