Concepts

Environments and keys

A workspace is one team or product. Inside it, every call carries an environment label: production, staging, development, or a short label of your own.

Why it matters

  • The dashboard shows Production by default, so test traffic does not inflate your real figures.
  • The switch under the workspace picker changes it: Production, Staging or All.
  • Prompt caching findings are counted on production only.
  • The monthly budget counts every environment, because every environment is on your provider bill.

The key decides

When you create a key you choose its environment. Every call sent with that key is filed under it, whatever the app says. A staging server cannot write into production by mistake.

Make one key per environment:

Where it runsKey environment
Production serversProduction
Staging or preview deploysStaging
Your laptop, CI, coding agentsDevelopment

Keys made before environments existed show any. For those, the app's own label is used: ZEXL_ENV for the SDK (default production), and development for Claude Code.

Key kinds

KindUsed byCan
SendThe SDK, Claude CodeSend call metadata. Cannot read anything
ReadThe MCP server, AI assistantsRead one workspace's figures. Cannot send or change anything

Create either kind in Settings > API keys. A read key can be limited to one environment or read all of them.

The salt and new keys

A send key ends with .<salt>. The salt is made in your browser (or by the MCP server on your machine) and never sent to Zexl. Calls are only compared with calls hashed with the same salt.

When you create a second send key, Settings asks for an existing key so it can copy the salt in your browser. Keep the same salt across all keys of a workspace, so a loop that spans two services is still recognised.

Revoking

Revoke a key in Settings > API keys. Zexl stops accepting it within a minute.