Actively maintained
OptimToken: AI and Compute Economics status
Answered our latest tool-list check 16 hours ago with 8 tools. It will be marked verified after 3 successful checks in 7 days.
- Answered (30 days)
- 2 of 2 checks
- Last seen working
- 17 Nov, 00:17 UTC
- Last commit
- 13 Nov 2026
- Licence
- MIT
Live checks
We call this hosted server's tools/list endpoint without credentials, from the public internet, every day while it answers and weekly otherwise.
- Answered
- Needs sign-in
- No answer
| Checked (UTC) | Result | Response time | Tools |
|---|---|---|---|
| 17 Nov, 00:17 | Answered | 3.4 s | 8 |
| 16 Nov, 00:17 | Answered | 7.7 s | 8 |
Tools (8)
Read from the server on 17 Nov 2026.
- compare-llm-models
- Browse and filter the whole LLM catalogue and get back a ranked table: price, quality (ELO), efficiency and capabilities. Use this when the user wants to SEE THE FIELD — 'show me models under $1/1M', 'which providers have vision models', 'list open-weight models above ELO 1300', 'the ten cheapest models for a coding task'. The table is ordered by Arena ELO unless `sortBy` asks for efficiency, cost
- estimate-llm-cost
- Cost a workload with EXACT numbers the caller supplies: arbitrary token counts per request and any monthly volume, not just the 10k/100k/1m presets the other cost tools use. Use this for 'about 800 in and 200 out, 4 million calls a month', or to price one named model across every use-case profile. To compare 2-4 named models like for like at a preset volume, use compare-models-side-by-side instead
- compare-models-side-by-side
- Compare 2-4 named LLM models against all 8 use-case profiles at a chosen monthly volume, showing list and optimized cost for each. Use when the user names specific models to weigh against each other, rather than filtering the whole catalogue. If they also supply their own token counts, or a volume outside 10k/100k/1m, use estimate-llm-cost instead. Every name is resolved against the catalogue and
- recommend-llm-model
- Pick a model. Returns a ranked top 3 for one workload under optional constraints, each with a per-constraint satisfied/violated breakdown as the evidence. Use this when the user wants an ANSWER rather than a table — 'what should I use for support tickets under $500 a month'. To browse or filter the whole catalogue instead, use compare-llm-models. Constraints: (monthly budget, minimum ELO, required
- compare-compute-pricing
- Compare cloud compute instance pricing across AWS, Azure, GCP, DigitalOcean, OCI, OVH, and Alibaba. Filter by region, provider, vCPUs, memory, category, processor, or use case. Use this for 'the cheapest 8 vCPU / 32 GiB instance in Europe', and for what a commitment saves: each row gives the Linux list price in USD per hour on demand, on spot, and under a 1-year and 3-year commitment (savings plan
- compare-model-hosts
- Who sells a model, and at what price. Most models are sold by several hosts (the model maker, a cloud platform such as Amazon Bedrock, Azure or Vertex, or an independent host) at different rates, and every other tool here quotes ONE of them. For 1-4 named models this returns how many hosts sell each, the cheapest, the dearest, the model maker's own rate, the spread between them, any promotional li
- estimate-self-hosting-breakeven
- API or own capacity: the monthly volume at which renting GPU instances costs the same as paying a model's API per token. An API bill grows with every request, a rented instance costs the same whether it is busy or idle, so below the break-even the API is cheaper and above it the fleet is. Give a model, a workload and either an instance from the compute catalogue (instanceType) or an hourly rate of
- track-llm-price-changes
- What moved. Every other tool here quotes today's price; this one says whether it has just changed, from the price archive optimtoken.optimnow.io keeps (its first day is `provenance.trackingStart`). Without `models` it returns the moves of the last 7 days across the catalogue: each model whose quoted price moved by 1% or more, with the price before and after and what the move does to a workload's m