IntentiAI

Find what inflates your AI bill before it ships

The IntentiAI cost audit reads your repository, finds every call to a language model, and flags the patterns that make the bill grow: loops with no limit, endpoints with no spending cap, and answers you pay for twice. It is free, open source, and runs on your machine.

npx intentiai

Node 20 or later. No API key. See a sample report.

What it looks for

Every rule describes a pattern that has cost real teams money, and most cite the research behind them. Each one has its own page with an example and the fix.

How it works

  1. Scan. npx intentiai finds each model call and the code around it: loops, retries, schedules, request handlers, guards.
  2. Price. Each finding is estimated against current public pricing for the model it calls, and a cheaper model is suggested where one fits.
  3. Report. You get a summary in the terminal and a private link to the full report: file, line, fix, and citation for every finding. Add --local to keep everything offline.

How accurate it is

On seven hand-labelled open-source apps, it found 98.6% of model calls. On five apps the rules were not written against, it found 45% of the labelled cost problems. The misses are listed in the repository. The rules are tuned to be right when they fire rather than to fire often.

Questions

How does the cost audit find model calls?

It reads your source statically. It recognises the official provider SDKs, LangChain, LiteLLM, the Vercel AI SDK, Spring AI, LangChain4j, LangChainGo and plain HTTP calls to provider endpoints, then checks each call site against 21 rules.

Do I need an API key or production traffic?

No. It runs on your machine against the code in your repository, before anything is deployed. Estimates use public pricing, not your usage data.

Which languages does it support?

TypeScript, JavaScript and Python get every rule with a real parser. Go, Java, Ruby and PHP get every call site and the 8 rules that need no deeper analysis. Other languages are counted and named as not scanned.

How is this different from LLM observability tools?

Observability tools such as Langfuse or Helicone measure traffic after you deploy. The cost audit reads code before you deploy, so it finds a loop with no limit before it runs. The two work well together.

LLM cost audit: find what inflates your AI API bill | IntentiAI