Retrieve an agent
Retrieve a single agent by its unique identifier. The response includes an available flag indicating whether the agent is within the team's plan limit and may be used for runs.
Path parameters
The unique identifier of the agent
Response
Agent details
Unique identifier for the agent
Name of the agent
Optional description of the agent
Optional base prompt for this agent
Default cloud environment ID for runs executed by this agent. The precedence order for environment resolution is:
- The environment specified on the run itself
- The agent's default environment
- An empty environment
Default runner UID for runs executed by this agent. When set, it overrides the selected environment's default runner for runs that do not specify their own runner_id. The precedence order for runner resolution is:
- The runner specified on the run itself
- The agent's default runner
- The selected environment's default runner
- The environment's legacy inline compute fields
- System defaults
Whether this agent is within the team's plan limit and can be used for runs
When the agent was created (RFC3339)
When the agent was last updated (RFC3339)
Ordered list of normalized skill specs associated with this agent. Always present; empty when no skills are attached.
Base model for runs executed by this agent. The precedence order for model resolution is:
- The model specified on the run itself
- The agent's base model
- The team's default model
MCP server configurations attached to this agent by default. Run-level MCP config takes precedence over this agent-level default.
Default harness for runs executed by this agent. The precedence order for harness resolution is:
- The harness specified on the run itself
- The agent's base harness
- Oz Deprecated - use harness instead, which carries the full {type, model_id, reasoning_level} default.
Default credential strategy for runs executed by a named agent.
- EXECUTOR: runs authenticate with the named agent's own credentials (e.g. a GitHub App installation token for the agent's team).
- CREATOR: runs authenticate with the credentials of the principal that created the run. Unlike the factory default, an agent may leave this unset. The strategy applied to a run is resolved in this order: the run's config.credential_strategy, then the agent's default, then the factory's default for factory-seeded agents, and finally EXECUTOR. The inherited strategy is validated at run creation time (the required credential must be mintable), like an explicit run-level value.
Whether runs created with this agent's API key may use the on_behalf_of field to attribute runs to another team member.
Default worker host for runs executed by this agent, or empty when unset. The precedence order for worker host resolution is:
- The host specified on the run itself
- The agent's default host
- The workspace default host