DevTools

Cursor

Cursor runs background ("cloud") agents against your repositories: you hand one a prompt, it edits code and can open a pull request.

Authentication

  • Admin API key
  • API key

Actions

Generic API request. Call any Cursor API endpoint on this connection, for the case where no shipped action covers it yet. The connection supplies the base URL, the authentication and the egress route, so only the path, query and body are yours to fill.

  • Add runSend a follow-up prompt to an existing cloud agent (POST /v1/agents/{id}/runs).
  • Archive agentDestructiveArchive a cloud agent; reversible via Unarchive agent (POST /v1/agents/{id}/archive).
  • Cancel runDestructiveStop an in-flight Cursor cloud-agent run — the way to abandon work that is no longer needed or has gone too long.
  • Delete agentDestructivePermanently delete a Cursor cloud agent.
  • Get agentRetrieve one cloud agent's metadata and configuration (GET /v1/agents/{id}).
  • Get agent usageRead the per-run token usage recorded for one Cursor cloud agent — what to call for cost attribution or to check consumption before starting more work.
  • Get API key infoIdentity behind the authenticated API key (GET /v1/me).
  • Get daily usageDaily usage metrics for the team, aggregated hourly (POST /teams/daily-usage-data).
  • Get runFetch the status and result of one Cursor cloud-agent run — the action to poll after starting a run to learn whether it is still working, has finished, or failed.
  • Get spendSpending for the current billing cycle (POST /teams/spend).
  • Get usage eventsGranular usage events with per-event cost breakdowns (POST /teams/filtered-usage-events).
  • Launch agentDestructiveLaunch a Cursor cloud agent with an initial prompt (POST /v1/agents).
  • List agent artifactsList the files a Cursor cloud agent produced, so you can see what a completed run left behind before fetching or acting on it.
  • List agentsList the Cursor cloud agents on the account, newest first — the entry point for discovering the agent id every run, artifact and usage action needs.
  • List audit logsRetrieve team audit log events (GET /teams/audit-logs).
  • List modelsModels available to cloud agents, with their selectable parameters (GET /v1/models).
  • List repositoriesGitHub repositories the authenticated key can launch agents against (GET /v1/repositories).
  • List runsList the runs of one Cursor cloud agent, newest first, to find a recent run id or review what an agent has been doing.
  • List team membersList every member of the team with their role (GET /teams/members).
  • Unarchive agentDestructiveRestore a previously archived cloud agent (POST /v1/agents/{id}/unarchive).

Triggers

  • Agent status changedStarts when a Cursor background agent reaches a terminal ERROR or FINISHED state, delivered by the agent's webhook instead of waiting for the next poll.
  • New audit log eventStarts when a new team audit log event (member changes, settings changes, and similar admin actions) is recorded in Cursor.
  • New or updated agent runStarts when a run of one Cursor cloud agent is created or its status changes, checked on a schedule.
  • New or updated cloud agentStarts when a Cursor background (cloud) agent is launched or its status changes, checked on a schedule.

Product names, logos and brands are the property of their respective owners and are used here for identification only. Their use does not imply endorsement by, or affiliation with, those owners.