First month free · 30-second install · Claude Code
Spend by feature
Rolled up from the linked Jira or Linear ticket
MER-100Checkout redesign$5,180
MER-140Search v2$4,020
MER-160Mobile onboarding$3,360
By developer
Top 3, June
alice@meridian.dev$4,210
ben@meridian.dev$3,560
chloe@meridian.dev$2,980
By repo
Top 3, June
meridian/api$6,240
meridian/web$4,810
meridian/mobile$3,120
June total$18,932
Illustrative figures from a synthetic example team, not a customer account.
Built by engineers from
The problem
The invoice arrives. Then the question arrives.
Which feature did this buy?
The invoice gives you one total for the month. It cannot tell you which piece of work that money turned into.
Who spent it, and on which repo?
Provider billing sees an API key. Not a developer, not a repository, not a branch, not a ticket.
Should any of it have happened at all?
A side project on the company account. A 2am run against a repo nobody authorised. Nothing is watching for either.
What Lineman is
One line of install, and every AI dollar arrives with a name on it.
Lineman sits alongside Claude Code, reads the git context around every call, and resolves each session to a developer, a repository, a branch and a ticket. That rolls up into spend per feature, alerts when spend breaks your rules, and a figure written onto the Jira or Linear ticket your team already tracks.
Why we see more
Everyone else reads the same API.We read your git history too.
Provider billing data can only report what it holds: a key, a user, a total. Lineman reads the git context around every call, so the same dollar arrives with a developer, a repository, a branch and a ticket already attached.
Provider console & API-only tools
A total for the organisation
Maybe a split by API key or user
No repository, branch or ticket
No idea which feature cost what
Nothing watching for spend that breaks policy
Lineman
Every call attributed to a developer and repo
Branch and ticket resolved from git context
Rolled up by feature and epic
Cost written onto the Jira or Linear ticket
Alerts on unauthorised repos and out-of-hours runs
Everything on the right is read from context your team already produces. No manual tagging, no per-call bookkeeping.
Cost Explorer
Turn one scary invoice into a managed line item.
Lineman tracks every Claude Code call and attributes it automatically. Pick a question on the left, see the answer on the right.
app.lineman.io/dashboard/cost-explorer/breakdowns
Last 7 days
Spend by repository
Total$18,932
meridian/api$6,240.0033.0%
meridian/web$4,810.0025.4%
meridian/mobile$3,120.0016.5%
meridian/infra$2,090.0011.0%
Other (5)$2,672.0014.1%
Spend by developer
alice@meridian.dev$4,210.00 / $3,800.00
ben@meridian.dev$3,560.00 / $3,800.00
chloe@meridian.dev$2,980.00 / $3,800.00
diego@meridian.dev$2,540.00 / $2,800.00
erin@meridian.dev$1,870.00 / $3,000.00
Cost on the ticket
The number lands where the work already lives.
Lineman writes AI spend onto the Jira or Linear ticket itself, so cost per feature and per epic is a fact in the tracker your team already opens every day, not an answer somebody has to go and assemble.
Nothing to tag, time or file. The running total is written back on Lineman's own schedule.
Every attributed session behind the ticket rolls up to the ticket, and every ticket rolls up to its epic.
Jira, Linear, GitLab, GitHub Issues, Azure Boards and ClickUp.
Illustrative figure, not a customer's bill: a worked example on the same synthetic Meridian team used across this page. The panel is a rendered reproduction of the Jira issue view, not a screenshot, and the field is a Jira number field, so Jira prints the value without a currency symbol.
Only in Lineman
Catch the spend that should never have happened.
A developer running a side project on the company account. A 2am run against a repo nobody authorised. A team quietly doubling its budget. No other AI cost tool watches for any of it, because none of them can see the repository.
Unauthorised-repo detection, so secrets and side-projects don't burn budget unseen
Per-team and per-member budgets, daily, weekly and monthly
Out-of-hours flags tuned to each developer's timezone
Root-cause on every spike: who, where, which model
Full spend audit trailExportable, per-developer and per-repo
Questions, answered
Frequently asked questions
The seven things teams ask before they roll Lineman out, answered plainly.
Two things. It prices every Claude Code session and tells you who spent it: which developer, which repo, which branch, which ticket. And it moves the data-heavy parts of a session, large file reads, build output, log triage, onto a cheaper secondary model, so your main model spends fewer tokens getting through them. You install it once and carry on working the way you already do.
Find out what your AI spend actually bought.
Controlling the spend costs about 2% of it. Add a card, get the first month free, then $14.99 a month with unlimited people on the account. Cancel any time before the month is up and you pay nothing.
Built by engineers from