Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
Unique identifier for the agent within the workspace
1 - 255The role or function of the agent
1A brief description of what the agent does
1Detailed instructions that guide the agent's behavior
The path where the agent will be stored in the project structure. The first element identifies the project, followed by nested folders (auto-created as needed).
With project-based API keys, the first element is treated as a folder name, as the project is predetermined by the API key.
"Default"
Model configuration for agent execution. Can be a simple model ID string or a configuration object with optional behavior parameters and retry settings.
A model ID string (e.g., openai/gpt-4o or anthropic/claude-haiku-4-5-20251001). The agent can be run with a wide range of models with different capabilities, performance characteristics, and price points. Only models that support tool calling (function_calling) can be used to run agents. See (supported models)[/docs/proxy/supported-models] documentation for the complete list of available models.
Configuration settings for the agent's behavior
agent display name within the workspace
255A custom system prompt template for the agent. If omitted, the default template is used.
1Optional array of fallback models used when the primary model fails. Fallbacks are attempted in order. All models must support tool calling.
Optional array of memory store identifiers for the agent to access. Accepts both memory store IDs and keys.
Optional array of knowledge base configurations for the agent to access
The agents that are accessible to this orchestrator. The main agent can hand off to these agents to perform tasks.
Response
Agent created successfully
1The status of the agent. Live is the latest version of the agent. Draft is a version that is not yet published. Pending is a version that is pending approval. Published is a version that was live and has been replaced by a new version.
live, draft, pending, published Entity storage path in the format: project/folder/subfolder/...
The first element identifies the project, followed by nested folders (auto-created as needed).
With project-based API keys, the first element is treated as a folder name, as the project is predetermined by the API key.
"Default"
Array of memory store identifiers. Accepts both memory store IDs and keys.
The agents that are accessible to this orchestrator. The main agent can hand off to these agents to perform tasks.
1Extracted variables from agent instructions
Agent knowledge bases reference