Keys & access
A key is your pass to the models. One account can hold as many keys as you need: per project, per client, per environment. They share a balance, but each can have its own limit.
How to get one
- Open API keys in your dashboard.
- Click “Create key”, name it, and set a limit if you want one.
- Copy the key right away — it's shown in full only once.
Best practices
| Practice | Why |
|---|---|
| A separate key per project | you can see each project's usage and disable one without touching the others |
| A limit per key | protects against an accidental loop or a leak |
| Key in an environment variable | keeps the key out of your repo and shell history |
| Rotate every few months | old copies of the key stop working |
# .env
RELAY_API_KEY=<key>
RELAY_BASE_URL=https://api.relaymodels.com/v1If a key leaks
Delete it in your dashboard — it stops working immediately — then create a new one and update your app settings. Your other keys and balance are unaffected.
Never expose a key in client-side website or mobile app code: requests to the models must come from your server.
Access via a code
If you received an activation code, a key is created on the /redeem page: enter the code, get a key, and see stats for your own keys only.