Why Choose a No Filter API?
Developers need a reliable uncensored LLM that does not refuse lawful adult content or controversial topics. Standard models often apply hidden filters that break roleplay scenarios or creative writing workflows. Our API provides direct access to a single tuned model with transparent pricing and no subscription tiers. You get consistent behavior without routing through multiple vendors with varying policies.
- No hidden refusals for lawful adult use.
- Transparent token pricing with prepaid credit.
- Direct model access without gateway routing.
Prerequisites for Integration
You need an API key and a client library that supports OpenAI-compatible endpoints. Our service works with any standard SDK by changing the base URL. You must handle streaming manually if you want token-by-token output. The model ID is always 'uncensored' regardless of the client you use. Context window support extends to 100,000 tokens for both prompt and completion combined. Max output per request is 16,000 tokens unless you specify a lower limit.
Step 1: Obtain Your API Key
Generate your key via the dashboard using Google or email authentication. The key appears immediately on the screen after creation. You can rotate keys by generating a new one, which replaces the old active key. Each account is limited to one active key at a time. There is no phone number requirement for signup.
Step 2: Configure Your Client
Set the base URL to https://api.aitextgeneratornorestrictions.com/v1 in your client configuration. Pass your API key in the Authorization header as a Bearer token. Use the model ID 'uncensored' for all requests. You can adjust parameters like temperature, top_p, and seed to control creativity. JSON mode is available by setting response_format to json_object. Function calling works with standard tool definitions.
This setup ensures compatibility with existing codebases. You do not need to rewrite your integration logic. The endpoint structure matches the official OpenAI API exactly.
Step 3: Make Your First Request
Send a POST request to /v1/chat/completions with your message array. Include the system prompt to define the model behavior. Set the model parameter to 'uncensored'. You can specify max_tokens to limit output length. The API returns a JSON object with the generated text. Errors are free, so you can test freely without charge. Use the example below to verify your connection.
Handling Streaming Responses
Enable streaming by setting the stream parameter to true. The API returns Server-Sent Events (SSE) for each token. Read the data field from each event to get partial content. The final chunk contains the total token usage for the request. This approach reduces perceived latency for long responses. It is ideal for chat interfaces and real-time applications. You can stop the stream early if the user changes their mind.
Implementing Function Calling
Define your tools in the tools array of the request. The model will return tool calls in the response if appropriate. Parse the function name and arguments from the response. Execute the function and send the result back in the next message. This pattern enables complex workflows and external integrations. Set tool_choice to auto or specify a specific tool. JSON mode is an alternative for structured data output.
Monitoring Usage and Costs
Track usage through the dashboard or by analyzing response headers. Credit is charged based on actual token consumption. Input tokens cost $0.15 per 1M tokens. Output tokens cost $0.50 per 1M tokens. Errors do not consume credit. Prepaid credit never expires. You can top up with USDT or USDC at any time. Bonus credit is applied automatically for larger deposits. Check your balance regularly to avoid service interruption.
Troubleshooting Common Issues
If you get a 401 error, verify your API key and base URL. Rate limits are 300 requests per minute per key. Connection limits are 8 concurrent requests per key. Request body size must be under 8 MB. If streaming stops early, check for network interruptions. Ensure your client handles SSE correctly. Use the support page for billing disputes or technical issues. Double charges are fixed through the support team.
