API & Reference > Technical Reference
Technical reference
# Technical reference Look up the programmatic interfaces for running and managing agents from CI pipelines, scripts, backend services, and custom tooling, without the Warp desktop app. ## API & SDK The [Oz API & SDK](/reference/api-and-sdk/) lets you create, monitor, and steer cloud agent runs over HTTP. Official SDKs for [Python](https://github.com/warpdotdev/oz-sdk-python) and [TypeScript](https://github.com/warpdotdev/oz-sdk-typescript) provide typed clients with built-in retries and error handling. - [Agent API reference](/api) - Interactive reference for every endpoint, parameter, and schema. - [API & SDK quickstart](/reference/api-and-sdk/quickstart/) - Create and monitor your first run in about five minutes. - [API keys](/reference/cli/api-keys/) - Create and manage the keys that authenticate API and CLI requests without human interaction. - [API error reference](/reference/api-and-sdk/troubleshooting/errors/) - Error codes, response format, and resolution steps. - [Demo: Sentry monitoring with SDK](/reference/api-and-sdk/demo-sentry-monitoring-with-sdk/) - A webhook handler that triggers agents from production errors. To work with a [Warp factory](/factories/) from your own code, use the [factory API](/factories/factory-api/) to discover a factory and dispatch work to it by UID, or connect an MCP-capable coding agent through [Factory MCP](/factories/factory-mcp/). Both are documented with the rest of the Warp Factories docs. ## CLI Two command-line tools run agents, depending on where the work happens: - **[Warp Agent CLI](/agents/cli/)** - Runs the Warp Agent interactively in any terminal, including over SSH and in the Warp app. Documented on the Agents tab. - **[Oz CLI](/reference/cli/)** - Runs and manages cloud agents from scripts, CI, and automated systems with the `oz` binary. It is being deprecated in favor of the Warp Agent CLI. The Oz CLI pages cover its full surface: - [API Keys](/reference/cli/api-keys/) - Authenticate the CLI without human interaction in CI pipelines, headless servers, and containers. - [Agent Profiles](/reference/cli/agent-profiles/) - Control what the agent can access, how it behaves, and where it can act, including file access, command execution, and MCP server usage. - [MCP Servers](/reference/cli/mcp-servers/) - Pass MCP server configuration to agent runs using the `--mcp` flag, by UUID, inline JSON, or file path. - [Skills](/reference/cli/skills/) - Run agents from reusable instruction sets stored in your repositories using the `--skill` flag. - [Warp Drive Context](/reference/cli/warp-drive/) - Reference saved prompts, notebooks, workflows, and rules from Warp Drive directly in CLI agent commands. - [Integration Setup](/reference/cli/integration-setup/) - Configure environments and connect external tools like Slack and Linear so you can trigger agents from outside the terminal. - [Troubleshooting](/reference/cli/troubleshooting/) - Find solutions to common CLI errors, including authentication issues, agent failures, environment problems, and Docker image issues.Help me use this reference: https://docs.warp.dev/reference/Look up the Agent API, the factory API, the Python and TypeScript SDKs, and the CLIs for running Warp agents from code.
Look up the programmatic interfaces for running and managing agents from CI pipelines, scripts, backend services, and custom tooling, without the Warp desktop app.
API & SDK
Section titled “API & SDK”The Oz API & SDK lets you create, monitor, and steer cloud agent runs over HTTP. Official SDKs for Python and TypeScript provide typed clients with built-in retries and error handling.
- Agent API reference - Interactive reference for every endpoint, parameter, and schema.
- API & SDK quickstart - Create and monitor your first run in about five minutes.
- API keys - Create and manage the keys that authenticate API and CLI requests without human interaction.
- API error reference - Error codes, response format, and resolution steps.
- Demo: Sentry monitoring with SDK - A webhook handler that triggers agents from production errors.
To work with a Warp factory from your own code, use the factory API to discover a factory and dispatch work to it by UID, or connect an MCP-capable coding agent through Factory MCP. Both are documented with the rest of the Warp Factories docs.
Two command-line tools run agents, depending on where the work happens:
- Warp Agent CLI - Runs the Warp Agent interactively in any terminal, including over SSH and in the Warp app. Documented on the Agents tab.
- Oz CLI - Runs and manages cloud agents from scripts, CI, and automated systems with the
ozbinary. It is being deprecated in favor of the Warp Agent CLI.
The Oz CLI pages cover its full surface:
- API Keys - Authenticate the CLI without human interaction in CI pipelines, headless servers, and containers.
- Agent Profiles - Control what the agent can access, how it behaves, and where it can act, including file access, command execution, and MCP server usage.
- MCP Servers - Pass MCP server configuration to agent runs using the
--mcpflag, by UUID, inline JSON, or file path. - Skills - Run agents from reusable instruction sets stored in your repositories using the
--skillflag. - Warp Drive Context - Reference saved prompts, notebooks, workflows, and rules from Warp Drive directly in CLI agent commands.
- Integration Setup - Configure environments and connect external tools like Slack and Linear so you can trigger agents from outside the terminal.
- Troubleshooting - Find solutions to common CLI errors, including authentication issues, agent failures, environment problems, and Docker image issues.