Agent-Scoped Keys - Zetta Docs

Agent teams can create API keys scoped to one agent.

Example key name

agent:aeon

An agent-scoped key can only access that agent’s data.

Cross-agent access is blocked

If a key scoped to aeon is used for luca, the request will fail.

{
  "error": "Key is scoped to agent 'aeon', not 'luca'"
}

Why use them

Agent-scoped keys protect agent teams from accidentally exposing broad access. Prefer them over global keys when embedding data in agent-owned surfaces.