Get started

Authentication

Application requests use Bearer API keys. Account and key management use your signed-in web session.

The key

Keys start with ul_ followed by a random secret. The complete secret appears only when you create or rotate a key. The application stores a hash for authentication and a short prefix for identification.

Create a separate key for each application or environment. Give it only the models and spending limits it needs.

The header

HTTP header

Authorization: Bearer $UNCENSOREDLABS_API_KEY

Send the key in the Authorization header on POST /v1/chat/completions. Dashboard cookies do not authorize public inference requests. The public model catalog can be read without a key.

Permissions and limits

Model allowlists restrict which approved models a key can call.
Spending, request, and concurrency limits are enforced before forwarding.
A suspended account or revoked key cannot start new inference requests.

Rotate or revoke

Rotate a key when replacing a secret. Revoke it immediately if it is exposed. Deleting a key hides its dashboard record and disables it while preserving the financial references needed for accounting.