Every person who uses the gateway has their own key. This page explains how keys work, what yours can do, and what to do if it stops working.

​
Where your key comes from

Keys are issued by the person who runs the gateway (the admin). You do not sign up and mint your own key — you ask the admin, and they create one for you and send it to you. The admin creates keys in the gateway dashboard. Each key belongs to one person.
The server keeps only a hash of your key. If you lose it, nobody can recover it — the admin creates a new one. Treat the key like a password: do not paste it into documents, chats or code repositories.

​
What your key can do

​
If your key stops working

Keys stop for three reasons:
1

Check it is not a typo

Keys are long. Re-copy it from the admin rather than retyping.
2

Ask the admin

Tell them the symptom. They can see the request log and whether the key is still active.
3

Get a new key if needed

If the old key is gone or revoked, the admin issues a new one. The old key stops working immediately.

​
When a key is reissued

If the admin replaces your key, the old one stops at once. Any tool or CLI still holding the old key starts failing with 401 until you update it. That is expected — update the key in your tools and continue.

​
Keeping your key safe

In a password manager or the tool’s own settings — not in a file that gets committed to version control.
No. Each key is one person, with that person’s budget. Sharing it mixes your spend and makes revocation affect both of you.
Tell the admin immediately. They revoke it and issue a new one. Do not wait — a leaked key can spend your budget.