# Technical reference

This section covers the programmatic interfaces for running and managing Oz agents in CI pipelines, scripts, backend services, and custom tooling.

## CLI

The [Oz CLI](https://docs.warp.dev/reference/cli/cli) lets you run and configure agents from any environment — locally, in CI pipelines, or on remote machines.

* [API Keys](https://docs.warp.dev/reference/cli/api-keys) - Create and manage API keys to authenticate the Oz CLI without human interaction, ideal for CI pipelines, headless servers, and containers.
* [Agent Profiles](https://docs.warp.dev/reference/cli/agent-profiles) - Use agent profiles to 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](https://docs.warp.dev/reference/cli/mcp-servers) - Pass MCP server configuration to agent runs using the `--mcp` flag, by UUID, inline JSON, or file path.
* [Skills](https://docs.warp.dev/reference/cli/skills) - Run agents from reusable instruction sets stored in your repositories using the `--skill` flag.
* [Warp Drive Context](https://docs.warp.dev/reference/cli/warp-drive) - Reference saved prompts, notebooks, workflows, and rules from Warp Drive directly in CLI agent commands.
* [Integration Setup](https://docs.warp.dev/reference/cli/integration-setup) - Configure environments and connect external tools like Slack and Linear so you can trigger Oz agents from outside the terminal.
* [Troubleshooting](https://docs.warp.dev/reference/cli/troubleshooting) - Find solutions to common CLI errors, including authentication issues, agent failures, environment problems, and Docker image issues.

## API & SDK

The [Oz API](https://docs.warp.dev/reference/api-and-sdk/agent) lets you create and monitor 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.

* [Demo: Sentry monitoring with SDK](https://docs.warp.dev/reference/api-and-sdk/demo-sentry-monitoring-with-sdk) - example integration


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.warp.dev/reference/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.