50% promotional credit
50% billing credit on Gemini 3.6 / 3.7 / 3.8 Flash
Free planning calculators for model APIs, AI agents, RAG, chatbots and cost per user. Current pricing registry, visible assumptions, no signup.
Explore calculators →One representative model from each provider, with current token pricing at a glance. Open a model for context rules and cost details.
Start from the business question you actually have: monthly bill, cost per user, cost per task, or whether a workload fits.
Estimate monthly API spend from input tokens, output tokens and request volume across major production models.
Calculate → Unit economicsCalculate LLM API cost per active user and compare it with your SaaS subscription price or product margin.
Calculate → Agent costEstimate AI agent running cost from task volume, multi-step model calls, retries and paid tool usage.
Calculate → RAG costEstimate retrieval-augmented generation cost including document embedding, retrieved context, generation and vector database spend.
Calculate → Chatbot costEstimate monthly chatbot API cost using conversation length, history, system prompts and reply size.
Calculate → CachingEstimate how much prompt caching can reduce repeated input-token costs for supported AI models.
Calculate → Batch processingCompare standard LLM processing cost with a configurable batch-processing discount for asynchronous workloads.
Calculate → Context planningEstimate prompt tokens and check whether text plus reserved output fits current model context windows.
Calculate → Traffic planningCalculate what 1,000 AI API calls cost for a chosen model and average input/output size.
Calculate → Model comparisonCompare modeled monthly API cost across major AI providers and production models using the same workload assumptions.
Calculate →4 active offers verified against official provider sources. Not sponsored.
50% billing credit on Gemini 3.6 / 3.7 / 3.8 Flash
Google for Startups AI cloud credits
OpenAI startup API credits
Anthropic Startup Program
A provider's dollars-per-million-tokens table tells you almost nothing about what a feature will cost at production traffic. A real estimate needs a workload shape: how many requests, how much context, how much output and how often.
TokenCOGS converts those moving parts into units product teams can reason about: cost per request, per user, per conversation, per task, per month and per year.
Pricing is synchronized from primary provider pages where supported, with a verified fallback snapshot if the live registry is unavailable. Every result is an estimate and should be verified before procurement or production budgeting.