Why you need an uncensored key
Standard LLM APIs often filter content based on corporate policies, which can interrupt creative writing or technical analysis. An uncensored key grants access to a model tuned to answer without those refusals for lawful adult use. This ensures your prompts reach the model exactly as written, without hidden moderation layers altering the output. We provide a single, dedicated model via a standard endpoint. This eliminates the variability of proxy services that route requests to different vendors. You get consistent behavior for every request. The model handles controversial topics, fiction, and security research without unnecessary gating. This stability is critical for automated pipelines where unexpected refusals break your workflow. Our API serves one open-weight model run on our own servers. It is not GPT, Claude, or any other vendor product. You control the input, and the model responds based on its training, not a third-party policy filter. This direct line ensures predictable results for your applications.
Creating your account
You create an account by visiting the Get API key page and choosing to continue with Google or entering an email and password. This process takes seconds and requires no phone number. The system generates a unique identifier linked to your identity. You receive trial credit immediately upon creation. This allows you to test the service before committing funds. The account structure is simple: one active key per account. If you need a new key, generating it replaces the old one. This keeps your integration secure. We do not collect excessive personal data. An email address is sufficient for recovery and billing notifications. The interface is designed for developers who want to start coding without filling out extensive forms. Your identity remains private unless you choose to link it. This streamlined setup reduces friction between signing up and making your first request. You can begin configuring your SDK client within minutes of creation.
Verifying your email
Verification ensures the account belongs to you and secures your prepaid credit. When you sign up with email, you receive a confirmation message. Click the link inside to activate your access. This step prevents automated abuse and ensures you can recover your key if needed. Google sign-ups skip this manual step because Google already verified your identity. Once verified, your account status changes to active. You can immediately view your API key. The verification process is fast and usually completes within seconds. If you do not see the email, check your spam folder. Our system sends the message reliably. This single step confirms your eligibility to use the uncensored model. It also links your account to the prepaid credit system. Without verification, you cannot add funds or use the API consistently. Keep your email accessible for billing alerts and support requests. This simple verification layer maintains the integrity of your developer account.
Retrieving your key
Your API key appears immediately after signup or verification. Locate it on the dashboard under the API key section. Copy this string and store it securely. It acts as your password for all requests. The key is unique to your account. Do not share it publicly, as anyone with it can use your credit. You can regenerate the key at any time, which invalidates the old one. This is useful if you suspect a leak. The key format is a standard alphanumeric string. It works with any OpenAI-compatible client. Set it as an environment variable in your code. This prevents hardcoding secrets in your repository. The key enables access to the chat-completions endpoint. It also allows you to list available models. Your key is the bridge between your application and the uncensored model. Protect it like any other sensitive credential. Regular rotation is a good practice for long-running projects.
Understanding rate limits
Rate limits protect the service from overload and ensure fair usage. You are allowed 300 requests per minute per key. This supports high-throughput applications without degradation. You can also have 8 concurrent requests at the same time. This parallelism is useful for batch processing. The request body size is limited to 8 MB. This accommodates large context windows up to 100,000 tokens. If you exceed these limits, the API returns a 429 error. Wait a few seconds and retry. The limit resets every minute. This is standard for API services. Our limits are generous enough for most developer needs. Streaming requests count toward the per-minute limit. Concurrent connections count toward the simultaneous limit. Monitor your usage via the dashboard. If you need higher limits for specific use cases, you can reach out. These limits ensure stable performance for all users. Plan your batch jobs to stay within these bounds for optimal results.
Adding crypto credit
You add credit by sending crypto to the provided address. We accept USDT on TRC20 or USDC on Base. The minimum top-up amount is $20. The maximum is $500 per transaction. You can send any whole amount within this range. The system credits your account automatically. Bonus credit is added based on the amount sent. Top-ups of $50 or more receive a 5% bonus. $100 top-ups get 10% bonus. $200 or more receive a 15% bonus. This bonus credit never expires. Errors and refusals do not consume your balance. You only pay for successful token usage. The price is $0.15 per 1M input tokens and $0.50 per 1M output tokens. No monthly fees apply. Your credit sits in your account until you use it. This model suits developers who want predictable costs. Credit is not refunded, but mistakes like double charges are fixed via support. Use a wallet you control for secure transactions.
First API call example
You make your first call by sending a POST request to the chat-completions endpoint. Use the official OpenAI SDK or any compatible client. Set the base URL to our service address. Include your API key in the authorization header. Specify the model ID as uncensored. Send your prompt in the messages array. The model returns text completions. You can enable streaming for real-time token delivery. Function calling and JSON mode are supported. Adjust parameters like temperature and top_p to control creativity. The response includes token usage in the final chunk. This example demonstrates standard usage. It works with Python, Node.js, and other languages. The endpoint handles JSON input and output. You can test it with a simple hello world prompt. This confirms your key works and the model responds. Use this as a template for your application. Expand the prompt structure as needed for your specific use case.
Troubleshooting common errors
Common errors include 401 Unauthorized and 429 Too Many Requests. A 401 error means your API key is missing or invalid. Check that you copied the key correctly. Ensure it is in the authorization header. A 429 error indicates you hit the rate limit. Wait briefly and retry your request. 400 errors usually mean malformed JSON or missing required fields. Verify your request body structure. 500 errors are rare and indicate a server issue. Check the status page or try again later. If you see unexpected content refusals, note that sexual content involving minors is always blocked. This is a hard limit. Other content should pass through. Clear your cache if you suspect stale data. Verify your model ID is set to uncensored. Check your token usage if you ran out of credit. These steps resolve most issues quickly. Keep your SDK updated for best compatibility.
Next steps for development
Start by integrating the SDK into your project. Configure the base URL and key. Write a simple script to send a prompt. Test different parameters to find the right tone. Implement error handling for rate limits and network issues. Add logging to track token usage and costs. Use streaming for better user experience in chat interfaces. Experiment with function calling for structured data extraction. Build a batch processor to handle large datasets. Monitor your credit balance regularly. Top up via crypto when needed. Share your use case with the community. Contribute to open-source wrappers if available. This API is designed for developers who need reliability. It fits into existing workflows seamlessly. Expand your capabilities by combining it with other tools. The uncensored model offers flexibility for creative and technical tasks. Start building today with a stable, predictable API.
