velqa.dev API keys — create, limit, and revoke keys (pay in dirhams)
Your sk-... API keys authenticate every request to velqa.dev. This guide covers creating a key from the dashboard, restricting which models it can call, setting Budget (USD), RPM, and TPM limits, and revoking a compromised key.
Prerequisite: verify your email
You must confirm your email address before you can create a key. If the "Create a key" button is locked, open the Overview and click "Resend email", then follow the link. See Accounts and sign-in.
Create a key
- Open API Keys in the sidebar.
- Click Create a key.
- Give it a name (optional but recommended, e.g. "Cline personal") so you can recognize it later.
- Confirm with Create key.
The full key, which starts with sk-, is shown only once, at creation. Copy it right away with the copy button and paste it into your tool or secrets manager. Confirm with "I copied my key" to close the dialog.
Once the dialog is closed, the list shows only a masked preview of the key — there's no way to reveal it again. If you lose it, create a new one and delete the old key.
The key list
The keys table shows, for each key:
- Name
- Key (masked preview only)
- Created
- Last used ("Never used" until the key makes a request)
- Active Limits
- Actions (limits, delete)
A revoked key gets a Revoked badge and can no longer be used.
Restrict which models a key can call
You can scope a key to a subset of models — handy for keeping a prototype key on cheap models only. From the Models section, choose "Manage enabled models for the key" and toggle each model on or off. A model that isn't available on your plan can't be enabled. See the full list in Models.
Set limits: Budget, RPM, TPM
Open a key's Limits action to set:
| Limit | Description |
|---|---|
| Budget (USD) | A spend cap in dollars for the key, with a Period: *Total* (single cumulative cap) or *Monthly* (resets each month). |
| Requests / min (RPM) | Maximum requests per minute for the key. |
| Tokens / min (TPM) | Maximum tokens per minute for the key. |
Each limit must stay under your plan's cap: you're splitting your plan's capacity across keys, not raising it. Leave a field empty to leave it untouched, and set at least one limit to save. Those plan caps are detailed in Rate limits.
You can also set an Expiration so a key stops being valid on a given date.
Revoke or delete a key
Use the delete action on the key's row to revoke it. Revocation is immediate: any request carrying that key is rejected. Do this as soon as a key leaks (public commit, shared log, lost machine), then create a new one.
Learn more
- Authentication — how the key is sent in your requests.
- Rate limits — the RPM / TPM caps per plan.