How to Track Cursor AI API Costs (BYOK & Subscription)

Cursor has two cost models running at the same time: a flat subscription (Pro at $20/month, Business at $40/seat) and a variable API charge when you use Bring Your Own Key mode. Neither the Cursor app nor any single provider dashboard shows you the total — you have to add them up yourself. This post explains where each cost comes from and how to track it in one place.

The two cost layers in Cursor

Layer 1: Cursor subscription

Cursor Pro ($20/month) includes a usage allowance of fast requests and a larger pool of slow requests. When you hit the fast limit, Cursor either throttles you or charges overage — but the app doesn't surface the dollar amount until the invoice arrives. Business plans ($40/seat/month) work the same way.

This is a fixed or near-fixed cost. The billing goes through Cursor directly, not through OpenAI or Anthropic, so it doesn't appear in either provider's usage dashboard.

Layer 2: BYOK (Bring Your Own Key)

In BYOK mode, Cursor proxies your requests through your own OpenAI or Anthropic key. The cost shows up in your provider account — not Cursor's. This means:

• OpenAI BYOK: costs appear in your OpenAI usage dashboard under whichever project or key you connected
• Anthropic BYOK: costs appear in the Anthropic Console
• Neither dashboard shows the combined Cursor + BYOK total

Why tracking Cursor costs is harder than it looks

The typical developer using Cursor ends up with spend scattered across three places:

1. Cursor invoice (subscription)
2. OpenAI invoice (BYOK for GPT-4o, o1, etc.)
3. Anthropic invoice (BYOK for Claude Sonnet or Haiku)

If you also use those same provider keys for production workloads, the Cursor traffic is mixed in with everything else — making it impossible to tell how much of your OpenAI bill is “Cursor helping me write code” versus “my app calling GPT-4o in production.”

How to isolate Cursor API costs

The cleanest solution is a dedicated API key for Cursor:

1. Create a separate OpenAI project (Settings → Projects → New project)
2. Generate an API key under that project
3. Paste that key into Cursor (Settings → Models → API key)
4. Track that project separately in your cost dashboard

This isolates Cursor traffic so you can see its cost clearly, regardless of what your production app is doing on your main key. The same approach works for Anthropic: create a new API key in the Anthropic Console and label it “Cursor BYOK.”

Tracking Cursor spend alongside your other AI costs

Once you have isolation sorted, the next problem is seeing it all in one number. Cursor Pro subscription goes to Cursor. BYOK costs go to OpenAI or Anthropic. If you also use Gemini or OpenRouter for other things, that's a fourth or fifth provider dashboard to check.

TryTokka tracks all seven major AI providers — OpenAI, Anthropic, Gemini, OpenRouter, Azure, AWS Bedrock, and Cursor — in a single dashboard. The Cursor integration reads your subscription tier and adds it as a fixed monthly cost alongside the variable API spend, so the dashboard shows your real total AI coding cost without manual addition.

You can also set a single alert threshold across all providers: “email me when total AI spend crosses $100/month” — instead of managing separate alerts in every provider console (most of which don't have alerts at all).

What to watch for in Cursor BYOK costs

The spend patterns that catch developers off-guard:

• Agentic tasks. Cursor's agent mode (Background Agent, long-context tasks) can run dozens of API calls per session. A single refactor task can use 50,000+ tokens. On gpt-4o at $2.50/M input, that's $0.125 per long task — but if you run 20 a day, it adds up to $75/month before you notice.
• Context size. Cursor sends your full file context with every request. Large files or multiple files open = large input token counts per call. Switching to Claude Haiku or gpt-4o-mini for routine tasks cuts this significantly.
• Slow vs. fast requests. On Cursor Pro with BYOK, fast requests (GPT-4o, Claude Sonnet) charge your own key. Slow requests may use Cursor's infrastructure. The billing split isn't always visible in the app — you need to reconcile your Cursor invoice against your provider usage to see which is which.

The cheapest setup for most indie developers

For a solo developer with moderate AI usage, the most cost-effective Cursor setup in 2026 is typically:

• Cursor Pro for included requests (covers most daily coding tasks)
• BYOK with gpt-4o-mini for agent tasks (17× cheaper than gpt-4o for tasks that don't need top-tier reasoning)
• Claude Haiku BYOK for autocomplete-heavy sessions (fast and cheap for short-context completions)

This splits cost between the flat subscription (predictable) and a small BYOK overage (variable but low if you use efficient models). Track the split monthly and adjust when one line item starts dominating.

FAQ