Quickstart: Connect your code to our uncensored API

Authentication and Base URL

Start by generating your API key on the dashboard using Google or email. You will then point your SDK client to our specific base URL to begin making calls. This setup ensures your requests reach the correct uncensored model immediately.

https://api.cheapestllmapiprovider.com/v1

Pass your key in the Authorization header with the Bearer scheme. Keep this key secure, as it grants access to your prepaid credit. A single key per account simplifies tracking your usage across different projects.

Sending Requests to /v1/chat/completions

Send your first text generation request to the chat completions endpoint with a simple JSON payload. You must include the model ID uncensored to access our specific large language model. This endpoint accepts standard parameters for temperature, top-p, and stop sequences.

Use the following curl command to verify your connection and receive a response.

Copycurl https://api.cheapestllmapiprovider.com/v1/chat/completions \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "uncensored",
    "messages": [{"role": "user", "content": "list 5 benefits of pay as you go pricing"}]
  }'

You can adjust the max_tokens parameter to control output length, keeping in mind the hard limit of 16,000 tokens per request. Responses are returned in standard JSON format compatible with existing tools.

Python SDK Integration

Initialize the OpenAI client with your base URL and API key to use familiar Python methods. This approach allows you to reuse existing codebases without major refactoring. Set the base_url explicitly to direct traffic to our servers.

Copyfrom openai import OpenAI

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

The SDK handles serialization and retries automatically. You can pass a list of messages to simulate a conversation history. This method works seamlessly with our 100k context window for long documents.

Node SDK Integration

Configure the Node.js client similarly by overriding the default base URL. This enables you to integrate our uncensored model into your existing Node applications. Pass your API key as an environment variable for security.

Copyimport OpenAI from "openai";

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

The client supports both promise-based and async/await patterns. You can stream responses directly to the console or a file. This flexibility makes it easy to build real-time chat interfaces or batch processing scripts.

Streaming Responses

Enable streaming by setting stream: true in your request parameters. This delivers tokens as they are generated, reducing perceived latency for end-users. The final chunk contains the total token usage for accurate billing.

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)

Handle the stream events to update your UI incrementally. This feature is crucial for applications requiring immediate feedback. Errors during streaming still provide usage data in the final chunk.

Limits, Errors, and Context

Monitor your request limits to avoid service interruptions. You are allowed 300 requests per minute and 8 concurrent requests per key. The maximum request body size is 8 MB. If you exceed these limits, you will receive a 429 status code.

A 401 error indicates an invalid API key. A 402 error means your prepaid credit is exhausted. Top up with crypto to restore service instantly. The model supports a 100,000 token context window for complex tasks.