Quick answer
Cursor documents included api agent usage as Pro $20; Pro+ $70; Ultra $400 in included monthly usage. Model selection and token consumption determine how quickly the included value is used.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| included API agent usageModel selection and token consumption determine how quickly the included value is used. | Pro $20; Pro+ $70; Ultra $400 in included monthly usage | Individual paid plans | CursorAug 22, 2026 |
Why does this limit matter?
Two users with the same plan can reach the allowance at different times because models have different provider costs.
This value is scoped to Individual paid plans; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Review the Cursor usage dashboard and the model used by expensive agent sessions.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Price-denominated included usage is not equivalent to a guaranteed number of requests.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related