API keys
Create, limit and revoke the keys your code uses to call ewpire.
Create a key
Open API in the app, choose Create key and give it a name that says where it will be used, such as backend-prod. You can set its limits at the same time:
- Requests per minute – 60 unless you set another, up to 1,000.
- Daily and monthly spend limits – in credits, optional.
The secret is shown once. Copy it into an environment variable or your secret manager before you close the dialog:
curl
export EWPIRE_API_KEY="ewp_live_..."Then check that it works:
curl https://ewpire.com/api/v1/models \
-H "Authorization: Bearer $EWPIRE_API_KEY"Keys and workspaces
A key belongs to the workspace that was active when you created it. Its requests are paid from that workspace's balance and show in that workspace's usage.
See and manage keys
The key list shows each key's name, its prefix (the part after ewp_live_), when it was last used and what it spent today and this month. From there you can change a key's name and limits.
Revoke a key
Revoke a key the moment you think it has leaked, or when a service no longer needs it. Revoking is immediate: the next request with that key gets 401 invalid_api_key. A revoked key cannot be restored; create a new one instead.
Rotating a key: create the new key, deploy it, then revoke the old one.