For teams on Claude Code, Cursor, Copilot and Codex

Know what your AI coding tools cost — per merged PR

CodeSpend pulls usage and seat costs from every AI coding tool your team pays for, matches them to developers and merged pull requests, and shows where the money is wasted.

Read-only admin keys. We never read prompts or code.

Example: 16-person team, October

Spent this month$7,223
Projected month-end$8,946
Cost per merged PR$31.40
Highest spender, 4 PRs merged$314 / PR
Idle seats (14+ days)5 × Cursor
Monthly savings found$5,966

AI coding spend stopped being predictable

Usage-based pricing means one long agent session can cost more than a month of seats. Most teams find out on the invoice.

4 months

Uber reportedly used up its full-year 2026 AI coding budget by April, then capped spend per engineer per tool.

DesignRush, 2026
8% in 2 hours

After GitHub Copilot moved to metered AI Credits in June 2026, one Pro+ user reported losing 8% of a monthly allowance in two hours.

gHacks, June 2026
> a salary

Gartner predicts AI coding costs will surpass the average developer’s salary by 2028 as token use climbs.

Gartner, June 2026

How much is your team likely overspending?

Move the sliders to match your team. The math runs in your browser; nothing is sent until you sign up.

API-billed Claude Code, Codex, Cursor overages, Copilot AI Credits.
Assumed to spend 4× a typical developer.
For example Cursor Teams $40 or Copilot Business $19.
Adjust the savings assumptions
Estimated monthly AI coding spend
Likely recoverable each month

    An estimate from the assumptions above, not a promise. CodeSpend replaces them with your real numbers.

    Get the real number for my team

    How it works

    Setup takes about 15 minutes for an admin.

    Connect admin keys

    Read-only keys for Anthropic, Cursor, GitHub and OpenAI. Claude Pro/Max users connect through Claude Code’s built-in telemetry.

    Match spend to output

    Costs are tied to each developer and their merged PRs, so you see cost per PR by person and team.

    Act on what it finds

    Idle seats, plans that would be cheaper flat-rate, premium-model overuse and teams heading over budget.

    Why not the tools you already have?

    Each covers part of the picture.

    OptionWhat it seesWhat it misses
    Personal trackers (ccusage, CodexBar)One developer’s own limits and usageNo team view, no budgets, no link to output
    API gateways (Portkey, LiteLLM)Traffic routed through your API keysSeat plans, Cursor, Copilot, Claude subscriptions
    Each vendor’s admin consoleThat vendor’s spendThe other tools, and what the spend produced
    CodeSpendClaude Code, Cursor, Copilot and Codex together, including subscription usersEarly product: four integrations so far