Agentmetry
Free · Open source
SOC and DevSecOps teams
Your API dashboard shows per-request token counts. It does not show you that a single Claude Code session burned $50 before lunch, or why prompt caching cut your bill by 40% last week but nothing this week. AgentMeter sits between your agent and that confusion.
AgentMeter runs locally — no cloud sync, no account creation, no vendor dashboard to log into — and parses the tool calls, token counts, and caching splits that CLI agents like Claude Code, Gemini CLI, Codex CLI, and Copilot CLI generate. It surfaces the three-tier cost structure that prompt caching creates (input, cached-input, and output tokens each priced differently), which the raw API bill flattens into noise. The value-multiplier calculation compares API spend against estimated developer time saved, giving you a number to put in front of a manager. The wall appears when you need alerting, real-time budget enforcement, or integration with a team billing system — none of that is here.
Bottom line: Pick this when one developer needs to understand where their Claude Code budget is actually going; plan something else when your team needs spend caps, shared dashboards, or alerts before the bill arrives.
Find your fit
More options in LLM Observability. Compare pricing, platforms, and features side by side.
Free · Open source
SOC and DevSecOps teams
Freemium
Developers building GenAI apps and agents
Most AI coding agent cost data arrives too late and too aggregated to act on. AgentMeter captures every tool call a CLI agent makes, tallies real token costs split across the three prompt-caching tiers, and reports totals per session and per project — all from a local `pip install` with no external dependencies. The core workflow is a CLI command against your local session logs: `agentmeter cost ProjectX` returns total spend, token volume, and call count in one line.
The differentiating capability is prompt-cache analysis. The vendor states that prompt caching splits costs into three token types at three different rates — input, cached-input, and output — and that AgentMeter makes this split visible where API dashboards show only aggregate numbers. For teams iterating on large context windows or repeated code-review prompts, knowing the cache hit rate for a session is the difference between tuning toward savings and guessing.
AgentMeter fits a single developer or a small team that wants local-only visibility into CLI agent spend without touching a vendor product. It breaks down when the need shifts to enforcement: there are no budget caps, no alerts when a session crosses a threshold, and no multi-user shared view. The tool is passive — it reads and reports, it does not intercept or block. Teams that discover they need spend governance rather than spend visibility will outgrow it quickly and move toward infrastructure-level controls or vendor-native quota tools.
The tool is open-source under the Apache-2.0 license, self-hosted by definition (it runs on the user’s machine), and installable via pip. It targets Claude Code as the primary integration, with stated support for Gemini CLI, Codex CLI, and Copilot CLI. The README notes a value-multiplier calculation that estimates API cost against developer time saved — useful for justifying agent usage to stakeholders who see only the invoice line.
Sign in to rate this tool or suggest an edit.