How to use the unfiltered ai chat API
The unfiltered AI chat API provides a straightforward, OpenAI-compatible endpoint for generating text without content refusals. Developers get a single, uncensored model with streaming, JSON mode, and a prepaid crypto-only economy, eliminating the friction of restrictive guardrails.
Key takeaways
- Send requests to POST /v1/chat/completions with the model ID "uncensored" to bypass standard content filters.
- Support for streaming via SSE, JSON mode, and function calling ensures compatibility with modern client libraries.
- Prepaid credit costs $0.15 per 1M input tokens and $0.50 per 1M output tokens, topped up via USDT or USDC.
- Each account gets one active API key with a 300 requests per minute limit, ensuring predictable scaling.
Why developers prefer an unfiltered AI chat endpoint
Developers choose an unfiltered endpoint when standard models refuse plausible adult or controversial topics. Most commercial APIs apply broad safety filters that block creative writing, roleplay, or medical discussions. Our service delivers a single uncensored model that answers without unnecessary refusals for lawful adult use.
You get consistent behavior across sessions. The model does not route your requests through multiple vendors. You send text in and get text out. This consistency matters for applications that require deterministic responses. You avoid the complexity of managing different model behaviors. The endpoint handles the heavy lifting. You focus on your application logic. The base URL is HTTPS://api.unfilteredaimodel.com/v1. It works with standard OpenAI SDKs.
Setting up your OpenAI-compatible client
Configure your client to point to the unfiltered AI chat endpoint by updating the base URL. Use the standard OpenAI Python or Node.js libraries. Pass your API key in the Authorization header. The model identifier is "uncensored". This setup works with any client that supports the OpenAI chat-completions protocol.
- Set the base URL to HTTPS://api.unfilteredaimodel.com/v1
- Use the model ID "uncensored" for all requests
- Include your API key in the header
- Verify connectivity with GET /v1/models
from openai import OpenAI
client = OpenAI(base_url="https://api.unfilteredaimodel.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)
Configuring parameters for NSFW content
Adjust temperature and top_p to control creativity. Higher values produce more varied and less predictable text. This is useful for roleplay scenarios. Lower values yield more deterministic responses. Use the stop parameter to define custom end sequences. The seed parameter allows for reproducible results during testing. Presence and frequency penalties help reduce repetition.
The model does not refuse lawful adult content. It handles nuanced topics well. Streaming via SSE enables real-time token delivery. You receive token usage in the final chunk. This helps track costs accurately. JSON mode ensures structured output when needed. Function calling allows tool integration. These features work together seamlessly.
Implementing streaming for real-time roleplay
Enable streaming by setting stream to true in your request. The API returns a sequence of Server-Sent Events. Each event contains a partial response. This creates a smooth user experience. You can display tokens as they arrive. The final chunk includes the total token usage. This helps you monitor costs in real time. Streaming reduces perceived latency significantly.
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)
Handling JSON mode for structured data
Use JSON mode to enforce structured output. Set response_format to json_object. The model returns strictly formatted JSON. This is ideal for extracting data or generating config files. It prevents formatting errors in downstream processing. You can parse the response directly in your code. No additional validation is usually needed. This feature works alongside function calling. You can define schemas for your tools.
import OpenAI from "openai";
const client = new OpenAI({ baseURL: "https://api.unfilteredaimodel.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);
Managing context windows in long conversations
The context window is 100,000 tokens. This includes both the prompt and the completion. You can send long documents or extended dialogues. The max output is 16,000 tokens per request. If you do not set max_tokens, it defaults to 2,048. Manage your context carefully to avoid truncation. Keep track of token usage. The API does not automatically truncate your input. You must manage the conversation history. This gives you full control over the context. Long conversations require careful token management.
Monitoring usage and controlling costs
Costs are $0.15 per 1M input tokens and $0.50 per 1M output tokens. You pay for real usage. Errors and refusals are free. Prepaid credit never expires. You can top up with crypto. USDT on TRC20 or USDC on Base are accepted. Minimum top-up is $20. Maximum is $500. Bonuses apply for larger amounts. +5% bonus from $50. +10% from $100. +15% from $200. Monitor your usage via the final streaming chunk. Track token counts in your application. Set up alerts for high usage. This helps prevent unexpected charges.
Troubleshooting common integration issues
Common issues include incorrect base URLs or missing API keys. Ensure you use HTTPS://api.unfilteredaimodel.com/v1. Check that your API key is active. You can have one active key per account. A new key replaces the old one. Rate limits are 300 requests per minute. Concurrent requests are limited to 8. Request bodies must be under 8 MB. If you encounter errors, check the status code. 4xx errors indicate client issues. 5xx errors indicate server issues. Consult the standard OpenAI error documentation for guidance.
Next steps: scaling your unfiltered AI chat application
Scale your application by managing rate limits effectively. Distribute requests across multiple keys if needed. Monitor token usage closely. Use JSON mode for structured data to reduce parsing overhead. Implement streaming for better user experience. Consider caching frequent responses. The prepaid model allows predictable budgeting. Crypto payments simplify international transactions. Get $0.50 trial credit. It lasts 7 days. Start building your application today.
Frequently asked questions
Is the unfiltered AI chat model truly uncensored?
Yes, the model does not refuse lawful adult, fictional, or controversial topics. It is tuned to answer without content refusals for lawful adult use. The only hard limit is sexual content involving minors, which is always refused. You can send requests for various adult themes without standard safety filters blocking them.
How do I pay for the API?
Payments are crypto-only. You can top up with USDT on the TRC20 network or USDC on the Base network. Minimum top-ups are $20 and maximum is $500. Bonuses range from +5% to +15% depending on the amount. Credit never expires and errors are free.
What is the pricing structure?
The price is $0.15 per 1M input tokens and $0.50 per 1M output tokens. You pay for real token usage. Prepaid credit is charged based on actual consumption. There are no monthly fees or subscriptions. You can start with a $0.50 trial credit that lasts 7 days.
Does it support streaming and JSON mode?
Yes, it supports streaming via Server-Sent Events (SSE) and JSON mode. You can set response_format to json_object for structured data. Function calling is also supported. These features work with standard OpenAI-compatible clients and libraries.
Your API key is one step away
Sign up, retrieve your key, update the base URL. The entire process takes seconds.