Skip to main content

See and manage your keys

My keys at app.zeldoc.ai/my-keys is for the people who use Zeldoc.ai API keys. With it you see what each of your keys has used, send yourself a new key in a key's place, and stop a key you no longer trust. You don't need a dashboard account: you sign in with the e-mail address your key was sent to.

Organization admins decide which keys appear there and for whom, at the end of this page.

Which keys you see​

  • Your own keys: every key sent to your address, such as a ZConnect key from an invitation, your ZDev key, or a key your admin e-mailed you from the dashboard.
  • Keys you share: keys your admin shared with you and others, typically the key a system such as n8n uses. They show Shared with and everyone they are shared with.

You see them in every organization they belong to, so a consultant working for several customers sees each customer's key in one place. You never see other people's keys.

Sign in​

  1. Open app.zeldoc.ai/my-keys, or select Hold an API key? See its usage on the dashboard's sign-in page.
  2. Enter the address your key was sent to and select Send sign-in link.
  3. Open the link in the e-mail and select Continue.

The link works once, within 15 minutes, and you stay signed in for 12 hours. The e-mail is in the language of the page you asked from, Danish or English. The page answers the same for every address, so if no e-mail arrives, check that you used the address your key was sent to, and ask your organization's admin which address that is. Asking again within a minute sends no second e-mail.

See a key's usage​

Each key shows its organization, the start of the key (such as sk-e52d4fea...), its models, the key fields your organization uses, and its monthly spending limit if it has one. Under Usage, pick Today, Last 7 days, This month or Last month to see the cost, requests, input and output tokens, and the same per model.

These are the figures zeldoc usage shows for the key, in US dollars as the gateway counts them. Zeldoc.ai's own models, such as ZDev, are covered by your subscription and show as $0. A ZDev key also shows how much of your plan's tokens you have used this month, and if your organization pays with prepaid credits you see how many it has left. You always see your own keys' usage, also where your organization's usage isn't shown in the dashboard.

Send yourself a new key​

Select Send me a new key when you have lost a key, it may have leaked, or you just want a fresh one. The new key has the same name, models and key fields, and it arrives as a one-time link like your first key did. The old key stops working at once, so put the new key wherever you used the old one, for example with zeldoc auth login or in your tool's settings.

For a key you share, the new key goes to you, since you are the one putting it in place. Everyone the key is shared with sees the new key in place of the old one.

Disable a key​

Select Disable to stop a key at once, for example when a laptop is lost. A disabled key refuses every request and shows who disabled it and when. Only your organization's admins can enable it again, or send you a new one.

Change a key's models​

Where your organization's admins allow it for a key, the key shows Change models. Tick the models the key may call. You can choose only from the models your organization allows for that kind of key; anything else is for your admins to add.

Creating keys stays with your organization's admins. If you need another key, ask them.

For organization admins​

Everything below happens on the API Keys page of the dashboard.

Which keys appear for whom​

A key you send someone by e-mail appears on their My keys automatically: ZConnect keys from an invitation, ZDev keys, and keys you create with Send it by e-mail. That key is that person's.

A key you created and copied yourself, and a system key such as the one n8n uses, belong to no one person. To let people look after such a key, share it:

  1. Select the people icon (Who manages this key) on the key's row.
  2. Enter the addresses of the people who may manage it, one per line, up to 20.
  3. Select Save. The addresses show under the key's name as Managed by.

No e-mail is sent; the people sign in on My keys themselves. Leave the list empty to stop sharing the key. A key sent to one person can't be shared, and a key a partner runs for you can't either.

See what people changed​

Under each key's name, the API Keys page shows the last change made to it on My keys, by whom and when: a key disabled, a new key sent in a key's place, or models changed.

When someone disables a shared key, or sends themselves a new key in its place, your organization's admins also get an e-mail, since whatever uses the key has stopped until someone acts. Nobody is e-mailed when people replace or disable their own keys, or change a key's models.

Let people change a key's models​

Select the chip icon (Edit Models) on the key's row, tick Let the people on this key change its models under the model list, and select Save. The option shows on keys that have a person or people on them. The key's person, or everyone it is shared with, can then choose the key's models on My keys, within what your organization allows for that kind of key, exactly as when you change them.

Send someone a new key​

Send new key on a key's row e-mails the person the key was sent to a new key in its place, with the same name, models and key fields. The old key stops working at once. This works for ZConnect and ZDev keys and for keys you sent from the API Keys page.

Organizations whose keys are read-only

If Zeldoc.ai keeps your organization's keys read-only for its admins, people still send themselves new keys and disable their keys on My keys. Who manages a key, and whether its people may change its models, are then set by Zeldoc.ai: contact the Zeldoc.ai team.