Answer: Each claimed agent can mint at most 30 tokens per minute, with bursts of up to 5 tokens then 25 per minute on a Cursor-managed VM, and bursts of up to 10 on a self-hosted worker. The socket accepts at most 8 connections at once, and clients should retry 429, 503, 500, 502, and 504 with backoff while treating 403 as fatal. Status: Confirmed Entry: tool/cursor/pricing-and-limits/oidc-rate-limits-errors Revision: 1 Digest: sha256:fa618223fab6d960 (changes whenever the content changes) Timeline: Created: 2026-11-13T12:25:09Z Last changed: 2026-11-13T12:25:09Z Last verified: 2026-11-20T12:36:29Z Next check: 2026-11-21T12:36:29Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Unit | Source | As of per-agent mint limit | 30 tokens per minute | tokens per minute | [1] | 2026-11-20 Cursor-managed VM burst | 5 tokens | tokens | [1] | 2026-11-20 Cursor-managed VM sustained rate | 25 per minute | per minute | [1] | 2026-11-20 self-hosted worker burst | 10 | tokens | [1] | 2026-11-20 max concurrent connections | 8 connections at once | connections | [1] | 2026-11-20 fatal status code | 403 | | [1] | 2026-11-20 body size limit | 4 KB | KB | [1] | 2026-11-20 Sources: [1] Anysphere. "cursor.com/docs/cloud-agent/identity.md". https://cursor.com/docs/cloud-agent/identity.md Role: primary. Accessed: 2026-11-20T12:36:29Z Quote: "Each claimed agent can mint at most **30 tokens per minute**." (Supports: per-agent mint limit) Quote: "A Cursor-managed VM allows bursts of up to 5 tokens, then 25 per minute." (Supports: Cursor-managed VM burst, Cursor-managed VM sustained rate) Quote: "A self-hosted worker allows bursts of up to 10." (Supports: self-hosted worker burst) Quote: "The socket accepts at most 8 connections at once." (Supports: max concurrent connections) Quote: "Treat `403` as fatal: this agent isn't allowed to mint." (Supports: fatal status code) Quote: "Body over 4 KB" (Supports: body size limit) Snapshot SHA-256: 80832f5c8f03007aaee23b12a2c2daa09b7268dad7a6205abdc95118a950fe2f (captured 2026-11-13T03:10:00Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T12:25:09Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:36:29Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:36:29Z Last attempt: 2026-11-20T12:36:29Z Notes and limitations: Extracted automatically from a single official source (section "Rate limits and errors"). Related: https://latestn.com/tool/cursor/pricing-and-limits/on-demand-usage-legacy How does on-demand usage work on legacy Cursor plans? https://latestn.com/tool/cursor/pricing-and-limits/origin-app-signing-key-limit How many active signing keys can a Cursor Origin app have? https://latestn.com/tool/cursor/pricing-and-limits/review-limits What are Bugbot's limits on PR size and bot-authored PRs? https://latestn.com/tool/cursor/pricing-and-limits/metadata-rate-limits What are the rate limits and errors for the Cursor Cloud Agent metadata API? https://latestn.com/tool/cursor/pricing-and-limits/muse-wonder-pricing How is Muse Wonder billed in Cursor and which plan pool does it draw from? https://latestn.com/tool/cursor/pricing-and-limits/notion-billing How is Cursor usage in Notion billed? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T12:25:09Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cursor/pricing-and-limits/oidc-rate-limits-errors/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/cursor/pricing-and-limits/oidc-rate-limits-errors POST: https://latestn.com/dispute/tool/cursor/pricing-and-limits/oidc-rate-limits-errors with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cursor/pricing-and-limits/oidc-rate-limits-errors?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What are the rate limits and errors for Cursor Cloud Agent OIDC token minting? Revision 1, last verified 2026-11-20T12:36:29Z. https://latestn.com/tool/cursor/pricing-and-limits/oidc-rate-limits-errors (accessed 2026-11-21T10:00:26Z). @misc{LatestN_tool_cursor_pricing_and_limits_oidc_rate_limits_errors_r1, title = {What are the rate limits and errors for Cursor Cloud Agent OIDC token minting?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cursor/pricing-and-limits/oidc-rate-limits-errors}}, note = {Revision 1; digest sha256:fa618223fab6d960; last verified 2026-11-20T12:36:29Z; accessed 2026-11-21T10:00:26Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/cursor/pricing-and-limits/oidc-rate-limits-errors