checkout-api
$3,184.52
41 PRs · $77.67 per PR
Your AI coding bill arrives as one number. SpendByTeam breaks it down by team, project, branch and client — so you can budget it, defend it and bill it.
October · month to date
$11,919.32
vs Sep
▲ 18.2%
Forecast
$12,634
Active devs
23
| Project | Client | Spend | Per PR | Budget |
|---|---|---|---|---|
| checkout-apiKST-482-rate-limits | Kestrel Logistics | $3,184.52 | $77.67 | 91% |
| ostara-patient-appOST-117-offline-sync | Ostara Health | $2,741.08 | $94.52 | 110% |
| design-systemDS-88-tokens-v2 | Internal | $1,906.40 | $33.45 | 87% |
| harbor-storefrontHP-203-cart-rewrite | Harbor & Pine | $1,622.77 | $49.17 | 81% |
| ingest-pipelineDATA-61-backfill | Internal | $1,288.15 | $71.56 | 107% |
Sample data. Teams, projects and clients are fictional.
Turn oneAI invoiceinto aper-projectledger yourCFOand yourclientsunderstand.The provider bill tells you the total. It doesn’t tell you which product, which client or which ticket the money went into. Now you’ll know.
How it works
Install
Each developer runs the installer once — or an admin pushes one managed settings file to everyone. No proxy, no shared API keys, no change to how people work.
npx spendbyteam init --token=sbt_ing_…Collect
Your coding agent already emits OpenTelemetry metrics: cost, tokens, sessions, lines changed. We switch on metrics only. Logs and traces — the signals that could carry content — stay off.
OTEL_LOGS_EXPORTER=noneAttribute
Repository → project → client, automatically. A tiny open-source hook adds branch and ticket, so you see cost per PR and per Jira ticket — not just per person.
repo → project → clientBy project, by team, by client, against budget. Switch the lens, keep the same numbers.
$3,184.52
41 PRs · $77.67 per PR
$4,522.18
▲ 12% vs September
$4,148.82
2 projects · 3 repos
110%
Over budget by $241.08
Built for CTOs, engineering leads and agency owners who have to explain the AI bill.
Every repository rolls up into a project. Merge several repos into one product.
Compare teams side by side, month over month, with an end-of-month forecast.
Branch and ticket IDs turn spend into cost per merged PR and per Jira ticket.
Org, team, project or client limits. Slack and email at 80% and 100%.
Group projects under clients and see exactly what each customer’s work cost.
A monthly, client-ready PDF with ticket ranges and an optional handling fee.
Open, admins-only or anonymous. Finance never sees per-person data.
Metrics only, attribute allowlist, open-source hook. Hosted in the EU.
On seat plans, see the API-equivalent value each team gets from its seats.
For agencies & software houses
Group repositories under clients, set a handling fee, and send a monthly PDF that shows exactly what AI-assisted work cost on their projects — with ticket ranges, never prompts.
Example: 20-developer agency, ~70% of AI spend on client repos
$7,200 / per month recovered
Pass-through at cost + 15% handling fee. See the maths →
Prepared for
Kestrel Logistics
Acme Studio
Report #2026-10-04
1–31 Oct 2026
AI-assisted development used on your projects this month, measured per repository. Source code and prompts are not collected.
| Project | Amount |
|---|---|
| checkout-apiRate limiting, carrier webhooksKST-470 – KST-498 | $3,184.52 |
| kestrel-driver-appPush notifications, offline queueKST-501 – KST-516 | $964.30 |
Generated by SpendByTeam · PDF · page 1 of 1
Content never leaves the developer’s machine: the exporters that could carry it are switched off, our endpoints discard anything that isn’t a metric, and what arrives is filtered through a fixed allowlist. The installer and hook are open source.
We receive
Cost, token counts, session ID, user email, repo URL, branch, ticket ID
Never
Prompts, responses, source code, file paths, shell commands, tool inputs
{
"session_id": "6f1c2a9e-4b7d-4e0a-9c55-0d2f8e1b7a43",
"event": "SessionStart",
"repo_url": "https://github.com/acme/checkout-api.git",
"branch": "KST-482-rate-limits",
"ticket": "KST-482",
"at": "2026-10-17T09:41:12Z"
}That’s it. Six fields, sent when a session starts or changes directory.
Per active developer, never a percentage of your AI bill. 14-day trial on paid plans, no card.
See the numbers before you talk about them.
forever
Start freeBudgets, forecasts and a monthly answer for finance.
per active developer / month
Start 14-day trialMost popular
Put the AI cost of client work on the client’s invoice.
per active developer / month
Start 14-day trialProcurement, security review and invoice reconciliation.
annual contract
Talk to salesClaude Code today, via its built-in OpenTelemetry metrics. Other agents are on the roadmap.
No. Logs and traces exporters are switched off, our ingest discards anything that isn’t a metric, and metric labels are filtered through a fixed allowlist. The full payload is on our security page.
About two minutes per developer with one npx command, or one managed settings file for the whole organization.
Anyone who sent at least one cost data point in the month. People who didn’t use an AI coding agent that month aren’t billed.
Yes. We show the API-equivalent value of usage, so you can see which teams and projects get the most out of the seats you already pay for.
In the EU. Default retention is 13 months and is configurable per organization.
Connect three developers free, forever. Add the rest of the team when the first report lands.