Teapot Router / Documentation
Create and manage API keys
Give each app its own key and understand expiry and spending limits.
Open workspaceCreate a key
- Sign in, open API keys, and select Create API key.
- Give it a recognizable name. Keys never expire by default; you can choose 7, 30, or 90 days instead.
- Use account balance is the default. To cap this key's cumulative usage, choose a separate key limit and enter an amount. Create the key.
A key limit caps usage of that key. Charges still come from your account balance; it is not an extra deposit.
Reveal, use, and revoke
- Select Reveal in the key list and copy the real key. Paste it only into a trusted client; never share it in a chat, screenshot, or public repository.
- Use separate keys for apps and environments so you can identify requests in Usage.
- If you stop using a key or suspect exposure, select Revoke. Clients using it will need a replacement.
A key alone does not guarantee a working model request. You also need balance, an enabled upstream channel, and an available model.