How does Cursor bill a team for AI usage, and how do you keep it in check?
Short answer: On Cursor Teams, each paid seat includes its own weekly usage pool. Usage beyond the pool, and third-party models, are paid from a prepaid balance the whole team shares. Admins can set a monthly additional-usage limit for the team, a default per-member limit and per-member overrides, and see per-member spend in the dashboard and Admin API.
How the bill is built
Per Cursor’s Teams pricing docs:
- Each paid seat has a weekly pool for Cursor’s own models. Pools aren’t shared between members.
- Third-party models are billed at public list API prices plus Cursor’s token rate, from the team’s prepaid balance, from the first request (with some exemptions Cursor lists).
- Additional usage stops when the prepaid balance is empty or the team’s monthly limit is reached, whichever comes first.
Older Teams plans use different seat types and on-demand usage, so check which plan your team is on before comparing numbers.
The limits admins can set
Admins set one monthly additional-usage limit for the team, a default monthly limit per member, and per-member overrides. When a member hits their limit, their paid additional usage stops; included weekly usage keeps working and other members aren’t affected (Cursor’s spend limits help page). Only admins can change these settings.
Start with the $150 burn-audit hour. One hour with an operator. You leave with a written map of the jobs, tokens and flows to cut or rebuild. Pay the hour, then we schedule the session. See a sample audit (example data) or try the free burn check.
Book the hour — $150 Operator pack — $625 depositAI Concierge — $2,000/mo
The pack is $1,250 for 10 hours; checkout takes the $625 deposit. Questions first? Email daniel@agenthiveinc.com or call our AI front desk demo at (320) 335-6186.
Where the spend usually comes from
Common sources of surprise spend: a few heavy users on third-party models, background or parallel agents left running, and auto top-ups nobody reviews account for most surprises. We check seat tiers against how people actually work, set limits that match, and flag the workflows worth rebuilding.
The three ways to work with us
- $150 burn-audit hour. One working hour. We map the agents, routines and flows your team runs and hand back a written list of what to cut, fix or rebuild.
- $1,250 operator pack ($625 deposit). Ten hours of build and fix work on the flows from the audit. The balance is due as the work is scheduled.
- AI Concierge, $2,000/mo. A senior AI operator on retainer: two 45-minute working sessions a month, unlimited async help between them, and a shared asset inventory. Month to month; cancel any month after the first 30 days.
Common questions
Should we move everyone to a bigger seat tier?
Only the people whose usage regularly runs past their pool. The audit shows who that is.
Does a team limit cut everyone off?
On current Teams plans, hitting a member limit stops that member’s paid additional usage only. Check Cursor’s docs for your plan, since legacy plans behave differently.
Do you also cover Claude Code?
Yes. Many teams run both; see our Claude Code team spend page.
Start with the $150 burn-audit hour. One hour with an operator. You leave with a written map of the jobs, tokens and flows to cut or rebuild. Pay the hour, then we schedule the session. See a sample audit (example data) or try the free burn check.
Book the hour — $150 Operator pack — $625 depositAI Concierge — $2,000/mo
The pack is $1,250 for 10 hours; checkout takes the $625 deposit. Questions first? Email daniel@agenthiveinc.com or call our AI front desk demo at (320) 335-6186.
Related
- How much does Claude Code cost a team, and how do you control it?
- We keep buying AI usage top-offs. What should we check before buying more?
- What spend controls should we put on our AI agents?
- Free AI agent burn check
More AI operator guides
AI spend and usage
- AI agent usage audit for teams: what it covers
- How to cut AI agent spend without breaking what works
- Why AI on-demand usage spikes, and how to find the cause
- Buying AI top-offs every month? Check this first
- AI routine drift, loops and redundant runs: how to stop them
- Scheduled AI workflow fallback: when a seat runs dry
- AI seats as a business-continuity risk: a plan for teams
- Onboarding staff onto AI bots safely: a rollout plan
- How to measure AI agent cost per workflow
- Fractional AI operator vs hiring an AI ops person
- AI ops for leadership teams: who owns the agents
- Agents re-reading long histories: why it burns usage
- AI agent spend controls: budgets, alerts and limits
- AI model routing for teams: right model for each task
- How to build an inventory of your team’s AI agents
By team and role
- AI operator for agencies: client AI work, run properly
- AI operator for e-commerce teams: catalog, support, content
- AI operator for SaaS teams: coding agents, support, GTM
- AI agent rollout plan for ops leaders: pilot to team-wide
- Fractional AI ops for founders of funded teams
- AI agent governance for teams: owners, access, limits, logs
- Claude Code team spend: what it costs and how to cap it
- Hiring an AI implementation consultant: what to expect
- Moving an AI pilot to production: why pilots stall
- Grok Bot usage audit: per-bot and per-routine cost
- Grok Bot team rollout: plan it before adding people
Outside facts link to their sources and were checked in November 2026; product pricing and limits change, so confirm on the vendor’s page. First Deploy is built and run by Daniel Graham at AgentHive Inc, Palm Coast, Florida. We don’t promise a savings figure before we’ve seen your setup.