Warp Platform API quickstart

Create your first cloud agent run with the Warp Platform API and check its status, in about five minutes. The API runs and manages cloud agents from CI pipelines, backend services, scripts, or custom tooling without the Warp desktop app.

To dispatch work through a factory’s named agents and workflow, use factory endpoints after this quickstart. The run-management steps below also apply to the factory run those endpoints create.

This short demo shows how the REST API can power agent-backed apps like PowerFixer, an issue triage bot built by the Warp team.

Prerequisites

• A Warp API key - Create one in the Oz web app and copy the raw value. Use a personal key if you want runs attributed to you, or an agent key to attribute runs to a cloud agent. See API Keys for the full flow.
• A cloud environment - Agents run inside a configured environment that includes repos and other dependencies. If you don’t have an environment yet, follow the Cloud Agents Quickstart first.

1. Set your API key

Export your API key so every command in this quickstart can authenticate through the WARP_API_KEY environment variable.

export WARP_API_KEY="YOUR_API_KEY"

Replace YOUR_API_KEY with the key you created earlier. Keys start with wk-.

2. Create your first run

Submit a prompt to start an agent run:

curl -X POST https://app.warp.dev/api/v1/agent/runs \
  -H "Authorization: Bearer $WARP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "prompt": "Scan the repo for outdated dependencies and summarize the findings.",
    "config": {
      "environment_id": "ENV_ID"
    }
  }'

Replace ENV_ID with your environment ID. Find it with oz environment list on the Oz CLI or in the Oz web app.

Note

The official warp-platform-sdk Python package and @warp-dot-dev/warp-platform-sdk TypeScript package wrap the same API with typed models, retries, and error handling.

The API returns a run_id immediately. The agent starts asynchronously, and you can check its status at any time with the run ID.

3. Check run status

Fetch the current state of the run. Replace RUN_ID with the run_id from step 2.

curl "https://app.warp.dev/api/v1/agent/runs/RUN_ID" \
  -H "Authorization: Bearer $WARP_API_KEY"

The state has the following possible values:

• QUEUED - The run is waiting to start.
• INPROGRESS - The agent is actively running.
• SUCCEEDED - The run completed successfully.
• FAILED - The run encountered an error. Check the status_message field in the response for details, then use the API error reference to interpret the error code.

These are the most common states. See the agent and run endpoints and the Warp Platform API reference for all possible values.

To list all recent runs:

curl "https://app.warp.dev/api/v1/agent/runs" \
  -H "Authorization: Bearer $WARP_API_KEY"

4. View the results

Once the run reaches SUCCEEDED, the response includes a session_link, a direct URL to the full run transcript, including commands executed, files changed, and agent output.

You can also view and manage all runs in the cloud agent dashboard.

Next steps

You created a run from the command line and read its state and transcript back.

• Agent and run endpoints - The configuration options and run lifecycle, with the Warp Platform API reference for every parameter, query filter, and response schema.
• warp-platform-sdk for Python and @warp-dot-dev/warp-platform-sdk for TypeScript - Typed request and response models, retries, and error handling.
• Sentry monitoring demo - A webhook handler that starts agents from production errors.
• Scheduled agents quickstart and integrations quickstart - Run agents on a schedule, or start them from Slack or Linear.