# Your Vendor's List Price Is Not Your Cost: Applying Real FinOps to Token Spend > Four mechanics that turn AI spend from a monthly surprise into a ledger: self-owned rate cards, price snapshots, tag-based chargeback, and blocking quotas. Canonical: https://www.gatellm.io/blog/token-finops/ > Self-owned rate cards, time-windowed price snapshots, tag-based chargeback, and cost quotas that actually block requests. (2026-09-15) Tags: FinOps, AI, LLM, Cost Optimization, Cloud Costs Cloud FinOps took a decade to mature: tagging discipline, allocable cost, budgets with teeth. Then AI spend arrived and reset the clock. For most organizations, "AI cost management" today is a monthly invoice, a shared spreadsheet, and a prayer. Three specific gaps do the damage. **List price is not your price.** You negotiated a discount, or a committed-use rate, or a private price on a specific model. Where does that number live? In an email. Your cost reports still compute at public list price, which means every report you show finance is fiction with a confident font. **Prices move, and history moves with them.** A model drops its price mid-quarter. If your cost system stores one price per model, historical months get re-priced retroactively — last month's report, already presented, is now wrong. You have polluted history with the future. **Overspend is discovered, not prevented.** By the time the invoice lands, the money is spent. "We'll watch it more carefully" is not a control. Fixing these is what turns AI spend from a surprise into a ledger. Four mechanics do most of the work. ## A rate card you own The foundational object is a rate card *you* own: the gateway computes cost from your prices, not from whatever the vendor's pricing page says today. Two consequences follow immediately. First, negotiated discounts, committed-use rates, and private pricing become representable at all — as data, not as a footnote in someone's inbox. Second, provider price changes stop being an emergency. A new rate card version goes into effect on a date; you do not have to reconcile a hundred reports by hand. If your cost numbers come from a vendor's public page rather than from a rate card you control, you are not doing FinOps. You are doing arithmetic on someone else's marketing. ## Price snapshots, not a single current price Store prices as time-windowed versions, not as a single "current" row per model. The reason is the retroactive re-pricing problem above. Cost must be computed against the price that was in effect *when the request happened*, which means the price has to be addressable as of a timestamp. A model that changed price on the 14th should produce different unit costs for the 13th and the 15th — and the report you sent on the 1st should stay true. This is the same discipline financial systems apply to exchange rates and SaaS systems apply to tax rates. Token pricing is not special; it just arrived late. ## Tag-based chargeback Attribution is what turns a total into a conversation. The useful dimensions are the ones your organization already uses for decisions: team, project, environment, cost center. Tag requests at the gateway so the tagging does not depend on every application team remembering to do it. The practical test: can you produce a per-team cost report for last month without asking anyone to run a script? If that takes a week of engineering, the data is not really allocable. ## Quotas that block Budgets need teeth. A quota that only emails you is a notification, not a control. The mechanics that matter are the enforcement actions: degrade to a cheaper tier, shed non-critical traffic, or refuse requests outright, in that order of preference. The specific policy is a business decision — what matters technically is that the gateway is able to act on it, in the request path, before the spend happens. It also matters that the same quota system works across providers. A budget that only covers one upstream is a budget with a hole in it, and traffic finds holes. ## The test of whether this is real A short self-assessment. If you can answer all four without caveats, your AI cost management is real: 1. Can you state your effective unit cost per model, including negotiated discounts? 2. Can you reproduce a report from three months ago and get the same number? 3. Can you split last month's spend by team? 4. Can you point to a request that was blocked or downgraded because of a budget? Question four is the one that separates cost reporting from cost control. Everything before it is necessary plumbing. ## Related - [Home](https://www.gatellm.io/index.md) - [Pricing](https://www.gatellm.io/pricing.md) - [Cost Calculator](https://www.gatellm.io/calculator.md) - [About](https://www.gatellm.io/about.md) - [Book a Demo](https://www.gatellm.io/demo.md) - [FAQ](https://www.gatellm.io/faq.md) - [Compare AI Gateways](https://www.gatellm.io/compare.md) - [Compare LiteLLM](https://www.gatellm.io/compare/litellm.md) - [Compare OpenRouter](https://www.gatellm.io/compare/openrouter.md) - [Compare Alibaba Cloud AI Gateway](https://www.gatellm.io/compare/alibaba-cloud.md) - [Compare Azure API Management](https://www.gatellm.io/compare/azure-apim.md) - [Compare Apigee](https://www.gatellm.io/compare/apigee.md) - [Compare Cloudflare AI Gateway](https://www.gatellm.io/compare/cloudflare.md) - [Compare Kong AI Gateway](https://www.gatellm.io/compare/kong.md) - [Compare Portkey](https://www.gatellm.io/compare/portkey.md) - [LiteLLM vs Kong AI Gateway](https://www.gatellm.io/compare/litellm-vs-kong.md) - [LiteLLM vs OpenRouter](https://www.gatellm.io/compare/litellm-vs-openrouter.md) - [LiteLLM vs Portkey](https://www.gatellm.io/compare/litellm-vs-portkey.md) - [Use Cases](https://www.gatellm.io/use-cases.md) - [Reduce LLM Cost](https://www.gatellm.io/use-cases/reduce-cost.md) - [High Availability](https://www.gatellm.io/use-cases/high-availability.md) - [Multi-Tenant Isolation](https://www.gatellm.io/use-cases/multi-tenant.md) - [Compliance & Audit](https://www.gatellm.io/use-cases/compliance-audit.md) - [Troubleshooting by Symptom](https://www.gatellm.io/use-cases/troubleshooting.md) - [Mixed Multi-Vendor Model Stack](https://www.gatellm.io/use-cases/mixed-model-stack.md) - [Self-Host AI Inside Office](https://www.gatellm.io/use-cases/self-hosted-office-ai.md) - [Token Usage Visibility & Attribution](https://www.gatellm.io/use-cases/token-ops.md) - [Token FinOps: AI Cost Allocation & Control](https://www.gatellm.io/use-cases/token-finops.md) - [MCP Tool Governance](https://www.gatellm.io/use-cases/mcp-tool-governance.md) - [Web Search for Every Model](https://www.gatellm.io/use-cases/web-search-grounding.md) - [Multi-Key Rotation & Standby](https://www.gatellm.io/use-cases/multi-key-pooling.md) - [Admission Control for Connected Clients](https://www.gatellm.io/use-cases/client-admission-control.md) - [Enforce Which Model Agents Actually Run](https://www.gatellm.io/use-cases/enforce-model-policy.md) - [No Model Choice on the Client](https://www.gatellm.io/use-cases/automatic-model-tiering.md) - [One Protocol, Any Model](https://www.gatellm.io/use-cases/one-protocol-any-model.md) - [Office / Microsoft 365 Add-in](https://www.gatellm.io/office-addin.md) - [Glossary](https://www.gatellm.io/glossary.md) - [Model Catalog](https://www.gatellm.io/models.md) - [SDK & Framework Integrations](https://www.gatellm.io/integrations.md) - [AI Coding Agents & Harnesses](https://www.gatellm.io/coding-agents.md) - [Security & Compliance](https://www.gatellm.io/security.md) - [Privacy Policy](https://www.gatellm.io/privacy-policy.md) - [Terms of Service](https://www.gatellm.io/terms.md) - [Cookie Policy](https://www.gatellm.io/cookies.md) - [Data Processing Agreement (DPA)](https://www.gatellm.io/dpa.md) - [Sub-processor List](https://www.gatellm.io/subprocessors.md) - [Security Questionnaire (CAIQ/SIG/VSA)](https://www.gatellm.io/trust.md) - [Incident Response & Support](https://www.gatellm.io/sla.md) - [Vulnerability Disclosure Policy](https://www.gatellm.io/vulnerability-disclosure.md) - [Open Source License Notice](https://www.gatellm.io/open-source-licenses.md) - [Version Support & Lifecycle (EOL)](https://www.gatellm.io/lifecycle.md) - [Engineering Blog](https://www.gatellm.io/blog.md) - [Your Agents Have More Permissions Than Your Employees: Governing MCP Tools at the Gateway](https://www.gatellm.io/blog/mcp-tool-governance.md) - [The $10k Invoice Problem: Five Ways to Cut LLM Spend Without Dumbing Down Your App](https://www.gatellm.io/blog/reduce-cost.md) - [llms.txt](https://www.gatellm.io/llms.txt)