How do I estimate each feature's usage share?

Multiply each feature's average tokens per call by its monthly call volume to get its token consumption, then express each as a percentage of the total. The allocator handles the normalisation if your percentages don't add to exactly 100.

Why normalise the shares?

So that 100% of your spend is always allocated, even if your entered percentages don't sum perfectly. If your three features are entered as 45, 30 and 25, they already sum to 100; if they sum to 90 or 110, each is scaled proportionally.

Should I use token share or call share?

Token share is more accurate, because cost is driven by tokens, not request count. A feature with few calls but huge prompts can cost more than a high-volume feature with tiny prompts.

Does this account for input vs output token pricing?

Not directly — it allocates a known total by share. For per-feature spend from first principles, estimate each feature's input and output tokens with the LLM API cost calculator first, then use those figures as your shares here.

Is my data sent anywhere?

No. Everything runs in your browser. No spend figures or feature names are uploaded, stored or logged.

Per-Feature AI Cost Allocator

Turn one API bill into a per-feature P&L

When everything goes through a single API key, your monthly LLM invoice is one opaque number. But your CFO wants to know which feature is driving cost — is it the summarizer, the chatbot, or the classifier? This allocator splits your total spend across features by usage share, giving you a clean per-feature cost line you can drop straight into a P&L or unit-economics model.

How it works

You enter your total monthly spend and a list of features, each with a usage share as a percentage. The tool normalises those shares so they always sum to 100%, then allocates the spend proportionally: a feature with a 45% share of token consumption gets 45% of the bill. Because cost is driven by tokens, the most accurate share for each feature is its token consumption — average tokens per call multiplied by monthly call volume — rather than its raw request count.

Tips for accurate attribution

Use tokens, not requests. A feature with long prompts can dominate cost even with few calls. Weight by tokens for a true picture.
Separate input and output. If features differ sharply in output length, estimate each feature’s cost with the cost calculator first, then feed those dollar figures back in as shares.
Track over time. Re-run monthly to spot a feature whose share is creeping up — that is usually where an optimization (caching, a cheaper model) pays off most.
Tag spend at the source. For ongoing accuracy, attach a feature tag or metadata field to every API call so your provider logs can confirm these shares.