Skip to main content

API keys

An API key lets your own code use the User Evaluation API: start studies, read study reports, pull clips.

API keys come with the Pro, Team and Scale plans. On Free, Create key is turned off. If a workspace moves to Free, its keys stay in the list but stop working until it upgrades again.

Create a key​

  1. Go to Settings → API & MCP.
  2. Under API keys, click Create key.
  3. Give it a name you'll recognise later, for example CI pipeline. Tick Read only if the key only needs to read, for example for an AI assistant through MCP.
  4. Click Create key, then Copy key.

The full key is shown only once. Keys start with ue_live_. We store only a fingerprint of it, so we can't show it to you again; if you lose it, create a new one.

What a key can do​

A key acts as you, with your workspace role. It can do what you can do in the app, up to Member rights: an admin's key can't change billing, team or security settings. A read-only key can read and ask Eva, but can't change anything. If you leave the workspace, your keys stop working.

See and revoke keys​

The API keys list shows each key's name, the start of the key (for example ue_live_7f3c), when it was created and when it was last used. The Usage chart shows calls made with the workspace's keys.

To revoke a key, click Revoke key in its row. It stops working straight away. You can revoke your own keys; admins can revoke anyone's.

Keep keys safe​

  • Treat a key like a password. Don't put it in client-side code, a public repository or a support email.
  • Use one key per app or script, so you can revoke one without breaking the others.
  • If a key might have leaked, revoke it and create a new one.