Trazum

Trazum

Understand your AI spend. Decide what to change.

Find where your AI usage costs money, choose a change, and check the result. Trazum analyses local usage logs and prompts, ranks opportunities such as caching and model changes, and keeps estimates separate from measured outcomes.

Open source · Local analysis · No provider key needed to get started

Start here: one command, no global install

Requires Node.js 20 or newer. npx may download Trazum from npm.

npx @trazum/cli bill

*Illustrative data from examples/claude-projects, not a customer result. Generated from the CLI output.*

With no path, bill reads the local sessions of Claude Code, Codex and Gemini CLI, names each folder it reads, and splits the result by agent, project and model, with each session's subagents and workflows under the project they ran for; --by day|week|month adds the period you ask for. On a subscription, this is API-equivalent cost, not what you paid. Unpriced models are reported as gaps. Local analysis does not upload your files.

Have a supported usage export instead? Pass its path:

npx @trazum/cli bill ./usage-export.jsonl

Supported inputs · Try sample data in your browser

Turn a report into a decision

For teams paying for API usage, the useful question is what to change next. Start with your largest workload, review the assumptions behind one finding, and evaluate quality before changing models or prompts.

1. Understand usage: bill shows the recorded cost and coverage gaps.
2. Choose one change: plan ranks opportunities from a normalized usage log.
3. Check the outcome: verify compares the saved plan with later usage, including cases where the evidence cannot settle the result.

Follow the first-report-to-verification walkthrough. A projected saving is not a guaranteed reduction in your invoice.

Using a subscription?

A smaller API-equivalent estimate does not reduce a fixed subscription fee. Use Trazum to inspect conversation growth, review redundant prompt text and set token budgets for instructions you control. Check task quality before keeping a shorter prompt. This does not automatically manage your agent's context or guarantee more messages under your provider's limits.

Subscription efficiency workflow.

In the [Tasks dashboard](https://trazum.vercel.app/?tab=tasks) and CLI/MCP 2.6.0: task efficiency connects Claude Code/Codex task usage, repeated-tool evidence, a reversible instruction policy and an explicit acceptance decision. Compare observed usage before and after a change without inferring success or guaranteed savings.

Keep or share a report

npx @trazum/cli bill ./usage-export.jsonl --html-out bill.html

PDF, CSV and Markdown exports are also available. Review the report before sharing it: it contains usage and cost information.

Pick your integration

Claude Code is the first native integration, not a provider lock-in. Codex session imports, normalized usage logs and provider exports feed the same core. MCP clients can query Trazum without having a native transcript adapter.

Harness, model and payment mode are separate facts. An API-equivalent estimate is not a subscription invoice; a model without a price remains a gap.

Explore advanced workflows, commands, architecture and limitations

Your agents spend money in a loop. This prices the call before it happens.

One agent costs what it costs. A fleet of them spends in a loop nobody is watching per iteration, and the bill arrives a month later as one number with no per-decision detail inside it.

Trazum installs into that loop. The MCP server's first tool is spend_guard, and it is the only one here whose trigger is not a sentence somebody types:

"May I spend this?"  ->  yes, no, or cannot-tell.

A refusal carries the cheaper ways to make the same call, each priced for that call and each naming what it assumes. The ceilings come from your trazum.config.json; the spend so far comes from the usage log your host already writes. Nothing is called and nothing is spent to answer.

claude plugin marketplace add Davmunrey/Trazum

claude plugin install trazum@trazum

That one line brings the skill and the MCP server. An agent that reads Agent Skills from the repository instead gets the same skill with npx skills add Davmunrey/Trazum. Every other MCP client reads the same mcpServers JSON, so Cursor (.cursor/mcp.json), Windsurf, Claude Desktop and the rest are one paste:

{ "mcpServers": { "trazum": { "command": "npx", "args": ["-y", "@trazum/mcp"] } } }

The server is listed on the official MCP registry as io.github.Davmunrey/trazum, and every release updates the listing.

[Or run it right now, without installing anything: the Playground](https://trazum.vercel.app/?tab=playground)

That link opens the CLI's pure subset running in the page, against sample files already loaded, through the same @trazum/core functions the terminal runs. Nothing you paste leaves your browser.

The argument, in one screenshot

*Real output, transcribed. Read the last two lines: the rules recovered $24.00 a month, and the advisory above them is worth $528.40, 22 times more. That gap is the entire argument for this tool.*

*Generated by npm run draw:architecture, not drawn. architecture-image.test.js fails the build if a package exists that the picture does not show, if the core takes a dependency while the picture says it has none, or if a third module is allowed to reach a network without the picture saying so.*

The prompt is the part everyone looks at, and usually the cheap part. In the run above, forty percent of the text came out and it moved 3.5% of the bill. What moved the rest was a question nobody was asking: does this task need the model it is running on?

Every figure has a receipt. Sixteen advisories, each priced per month and reproducible on a single file: caching you are not getting, work that could go through the Batch API, a schema costing tokens on every call to describe a shape the request could carry as a parameter. Underneath them, twelve deterministic rules that shorten the text itself: same input, same output, free, offline, and never touching code, URLs, email addresses or placeholders. On top, an optional LLM pass for the compression rules cannot do, through whichever provider you configure, which never runs unless you ask.

                      ┌──────────────┐

│ @trazum/core │ the library: rules, tokens, pricing └──────┬───────┘ zero dependencies, browser-safe ┌────────────┬─────────────┼─────────────┬─────────────┐ @trazum/cli @trazum/mcp trazum-vscode @trazum/web action/ 55 commands MCP server the editor Next.js comments on for your agents status bar pull requests

@trazum/tokenizer-openai optional: exact counts for OpenAI install it or do not, nothing else changes

Contents

Limitations · Privacy · Pricing · Contributing

What it actually does

The analyser reports sixteen findings, with assumptions attached to each estimate.

1. Tells you where the money actually is. This is the part worth reading first, because it is where the numbers are. Every advisory is priced per month against your own call volume, and none of them is about making the text shorter:

| Output format stated twice | A schema shown in a code block and then walked again in prose. The block is the version worth keeping.