Skip to main content

​
Overview

Agent Key is a lightweight credential used to manage an agent on the mulerun platform. It is scoped to a single agent (application) and intended for agent-management operations such as sessions, configuration, and metering. Agent Key is distinct from MuleRun API key used to consume platform resources (LLMs, compute, etc.). An API key grants access to platform resources at an account level; an Agent Key grants management-level access at an agent level.

​
Key properties

  • Prefix: every Agent Key begins with ak_.
  • Scope: agent-level only. An Agent Key must be presented together with the corresponding agent ID for authorization.
  • Resource access: Agent Keys cannot be used to call LLM or other platform compute resources (status as of 2025-09).
  • Multiplicity & limits: one agent may have multiple keys; current limit is 10 keys per agent.
  • Default key: an Agent Key is created automatically when an agent is first created.
  • Deletion constraint: an agent must always have at least one key — deleting the last key is not allowed.

​
Who should use Agent Keys

  • Creators who need programmatic, agent-scoped access to manage sessions, workflows, or call agent-management and metering APIs without using account-level credentials.
  • Integrations (services, automation) that operate on behalf of a particular agent rather than on behalf of the entire user account.
  • Devices or services that should be limited to a single agent’s surface area for security and separation of concerns.

​
Typical scenarios

  • A third-party service calls mulerun APIs to open/close sessions for a specific agent.
  • A CI/CD job updates agent configuration or deploys a new workflow for a single agent.
  • A device or server component reports usage or queries metering endpoints for a particular agent (Metering API will accept Agent Keys).
⌘I