Manage API keys across your chat apps

Use separate named credentials for different clients while keeping one UnsavedAi account.

Give each app its own key

Create a named key for each client or environment, such as SillyTavern, Chat server, or Development. Save the full value when it is first shown; stored keys are masked. Key management availability is shown in your console.

Replace credentials safely

Create a replacement, update the relevant application, and test it before revoking the old key. Revocation removes that credential; it should not require changing unrelated clients.

Limits belong to the account

Multiple keys do not multiply your plan concurrency or request-rate allowance. They separate credentials, not subscriptions. UnsavedAi plans do not use per-key monetary budgets.

Your next step

Check available models, open your console, or read the API documentation. Public signup and paid plans are still being prepared.