# /v0/agents* is deprecated

Cursor API deprecated /v0/agents* without giving a shutdown date yet.

Cursor API deprecated the /v0/agents* endpoints without announcing a shutdown date. Existing /v0/agents* calls remain available during a migration window, but they will eventually fail once the legacy endpoints are removed.

## What to use instead

Use the Cloud Agents API v1 instead, where POST /v1/agents creates a durable agent and POST /v1/agents/{id}/runs carries each prompt. Because v0 remains available with no end date and v1 is currently a public beta without webhooks, moving off v0 is your team's call.

v0 remains available with no end date, and v1 is a public beta without webhooks: moving off v0 is the team’s call.

- API: Cursor API (api.cursor.com)
- Kind: Endpoint removal
- Takes effect: no date given yet
- Calls after that day: fail
- Calls it hits: `/v0/agents*`
- Source: [Announcement](https://cursor.com/docs/cloud-agent/api/v0)
- Verified: November 6, 2026, against Cursor API's own pages
- Page: https://www.okapi.bot/providers/cursor/breaking-changes/v0-agents-is-deprecated/

## Cursor API's words

> This page documents the legacy v0 API. New integrations should use the current Cloud Agents API, which reorganizes resources around a durable agent and per-prompt runs. v0 remains available during the migration window.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent