Create Agent
/v1/agentsCreate a reusable Agent configuration that bundles a catalog model, instructions, capabilities, and metadata. Model IDs use vendor/model form. Unknown request fields are accepted and ignored.
Request body
Send a JSON object with the agent configuration.
Available vendor/model identifier or {id, effort?, speed?}. Responses always use the structured object.
Human-readable Agent name.
Short explanation of the Agent's purpose. Null is accepted as an empty string on creation.
System instructions that define the Agent's behavior. Null is accepted as an empty string on creation.
Built-in toolset and custom tool configurations. Omission installs the default Agent toolset; explicit null does not.
MCP server configurations available to the Agent runtime.
Skills available to the Agent runtime.
Agent handoff configurations.
Application-defined JSON metadata. The platform-owned _sandbase namespace is stripped from public requests.
Agent object
Fields returned for an agent resource.
Stable identifier beginning with agent_.
Configuration version, beginning at 1 and incrementing after a successful change.
RFC 3339 timestamp set after the agent is archived.
Time the agent was created.
Time the current version was last updated.
Model choice
SandBase is multi-model. The model field accepts any available model identifier from the SandBase catalog.
Tool execution
Built-in tools run inside the managed agent runtime. Custom tools are executed by your client after an agent.custom_tool_use event.
Errors
invalid_requestA required field is missing or a field has an invalid value.
authentication_errorThe API key is missing or invalid.

