Manage RocketKey API keys: create, rename, block, regenerate, delete
Create a key per machine, rename, block, regenerate a leaked key, delete keys and see usage per key in the RocketKey dashboard.
Updated 25 Oct 2026
Everything about keys lives in Dashboard → API keys. You can create several keys (one per machine or tool), rename, block, regenerate and delete them at any time. All keys of an account share one daily USD allowance and the plan's requests-per-minute limit: more keys do not mean more allowance.
No plan yet? Read Get started first.
How many keys does each plan allow?
| Plan | Max keys | Requests per minute |
|---|---|---|
| Mini | 1 | 30 |
| Starter | 2 | 60 |
| Pro | 3 | 120 |
| Max | 5 | 240 |
Figures from Pricing. The API keys page shows keys in use over the maximum, for example 2/3 keys. At the limit, delete a key you no longer use to create a new one.
Create a key
- Go to Dashboard → API keys and click Create key.
- Name it after the machine or tool that will use it, for example
MacBook,work laptop,CI. Names are 1-40 characters and must be unique. - Click Create key. The key is shown once only: copy it now, then click I have saved the key.
RocketKey keeps only a hash of the key plus a short prefix and the last 4 characters so you can recognize it in the list. Nobody, support included, can show you the full key again. If you lose it, use Regenerate (below).
If your plan was just activated, a new key can show Activating… for a few minutes. The page updates by itself; there is nothing else to do.
Where to use the key
The same key works in every tool; only the setup differs:
- Claude Code: the
ANTHROPIC_BASE_URLandANTHROPIC_AUTH_TOKENvariables. See the Claude Code guide. - Codex CLI:
config.tomland theROCKETKEY_API_KEYvariable. See the Codex guide. - Cline and Cursor: the Base URL and API key fields in their settings. See Cline, Cursor.
- Your own code (Python, Node.js): see Call the API from Python and Node.js.
Test a new key with the free curl command in step 3 of Get started.
Reading the key list
Each row shows:
- Name and Key: the name you chose and the masked key (prefix and last 4 characters).
- Created and Last used: a key unused for a long time is a candidate for deletion.
- Today and 30 days: the USD that key spent, so you can see which machine uses the most.
- Status: Active, Blocked by you, Plan expired — key paused, or Applying… while a change syncs.
Rename, block, regenerate, delete
Open the Actions menu at the end of the key's row:
| Action | Effect | When to use it |
|---|---|---|
| Rename | Changes the display name only; the key stays the same. | New machine, new purpose. |
| Block | Every request with the key is refused until you unblock it. Can take up to a minute. | Pause one machine without reinstalling the key. |
| Unblock | The key works again within seconds if the plan is active. | Resume a blocked key. |
| Regenerate | The old key stops at once; you get a new key (shown once) with the same name. | Lost key, or a key you think leaked. |
| Delete | The key stops at once and cannot be restored. Its usage history is kept. | Retire a machine or tool. |
After Regenerate, put the new key on every machine that used the old one, or those machines get error 401.
Usage per key
Dashboard → Usage shows cost, requests and tokens per day in Vietnam time (GMT+7), updated every 2 minutes:
- The Breakdown section has By model and By key views: which model and which machine spend the most.
- Request log lists each request: time, model, tokens, cost and a short error. RocketKey does not store prompt content.
- Export CSV downloads the selected date range.
When the day's total reaches the allowance, every key gets error 402 until 00:00 (GMT+7). Sending too many requests at once gives error 429. To make the allowance go further, see Save allowance in Claude Code.
Keep keys safe
- One key per machine and per tool: if a machine is lost or a key leaks, block or regenerate just that key.
- Never paste a key into code, screenshots, issues or public repositories. Keep it in an environment variable or a config file outside the repo.
- Unusual spend on one key in the By key view: regenerate that key right away.
When the plan expires
Keys are not deleted. They switch to Plan expired — key paused and work again as soon as you renew, with no reinstall. See your plan under Dashboard → Plan & billing.