LLMeter helps developers compare language models and understand what using them could cost. You can explore prices and capabilities, estimate a workload, and look for cheaper options before choosing a model. It’s free to use, with no account or API key required.
I built it because comparing model prices meant jumping between provider pages and doing the math myself. It has helped me estimate costs in my own work. I wanted other developers to have the same place to check their numbers and compare options.
What you can do
- Explore and compare models. Search by model or provider, filter by capabilities, and compare up to four models side by side. See prices, context limits, and the providers offering each model.
- Estimate your costs. Enter input and output token counts, or paste text for a rough token estimate. Compare the same workload across models, check standard, cached-input, or batch pricing where available, and project a daily or monthly budget.
- Find models that fit. Choose the capabilities and context size you need, then rank matching models by price or the estimated cost of your workload.
- Look for cheaper alternatives. Start with a model you already use and explore lower-priced candidates with matching capabilities and at least as much context. A default filter keeps candidates in the same curated model class or above.
- Check your usage. Enter monthly token counts or import OpenAI usage and cost CSVs. Compare list-price estimates with what you paid and explore potential savings. Files are processed in your browser; your bill details aren’t added to shared links.
- See pricing changes. Browse price cuts, increases, new listings, and removed listings between data updates.
Model pages, filters, and calculator inputs can be bookmarked or shared, so you can send someone the comparison you’re looking at.
Making comparisons useful
A cheaper model still needs to work for your application. LLMeter compares declared capabilities and curated model classes; it doesn’t benchmark models or promise equal performance. Missing prices stay unknown, and the app flags retired models, unusual prices, and pricing it can’t fully represent.
Prices come from periodically updated data, so the app shows when they were last refreshed. Cost estimates are a starting point for planning; check the provider’s current rates before relying on them for billing.
I’m continuing to improve LLMeter and will add more tools as I find new ways to help developers understand their costs and choose models.