Start
How to issue an API key
The API key is created in @uncensobot with the API button and shown once. Copy it immediately — like the Base URL, no separate cheat sheet.
There is no web cabinet: issue, balance, and revoke live only in the bot. The key is SHA256-stored and not bound to a domain — only the client Base URL changes.
Issue
Open the bot, tap API. A new key replaces the old one — the previous key stops working. One-time display: save it to a password manager or IDE settings.
Then Base URL https://uncensored.monster/v1 and model z-ai/glm-5.3-flash-uncensored (or empty model routes to GLM). Full path in how to start.
Where to paste it
Into the client API key field — OpenAI-compatible SDKs, Cursor, Continue, curl. Protocol is Chat Completions only: not Anthropic Messages, not Responses, not embeddings.
Why a custom Base URL is in the OpenAI-compatible API note. Codes 401, 402, 404 are in the error breakdown and docs.
Revoke
API button again — issue a new key, the old one dies. If the key leaked, do not wait: reissue and update the client.
The key is not domain-bound and needs no origin whitelist. Any HTTPS client works while balance is positive.
Balance
The API bills the bot balance. Zero free calls. Packs $1, $5, $10, $25, $50, $100 — Crypto or xRocket USDT. Minimum per request $0.005.
FAQ
Can I view the key again?
No. Reissue through the API button only.
Do I bind the key to localhost or a domain?
No. The key is not domain-bound. Change only the Base URL to https://uncensored.monster/v1.
Does the bot key work on api.openai.com?
No. It is only for uncensored.monster/v1.