Cursor API
/v0/agents* endpoint removal
Deprecated, no dateSubscribe to Cursor APIShare
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.
Calls it hits
/v0/agents*
What to use instead of these calls
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.
In 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.
Facts
- API
- Cursor API
api.cursor.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Cursor API's own pages
Questions
When does this change take effect?
Cursor API deprecated /v0/agents* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Cursor API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Cursor API 1
-
No date
/v0/repositoriesEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.