Compare models

Track model prices and retirements

Should we keep, re-price or replace the current model after a price change, release or retirement notice?

What to compare

  • provider, model identifier and platform
  • price basis and effective date
  • announced retirement or shutdown date
  • recommended replacement and its limits
  • quality and cost measured on our own test set

Read the sources

  • Anthropic API pricing ↗

    Provider definitions for input, output, caching and feature-specific model charges.

    Public pricing documentation. No paid model call is made by this collection. A calculated estimate is not an invoice. Recheck the exact model, region, token basis and effective date.

  • Claude models overview ↗

    Current Claude models with API identifiers, context windows, output limits, knowledge cutoffs and retirement commitments.

    Public documentation. Cloud platforms that offer the same models can use other identifiers and set their own lifecycle dates. Listed limits and cutoffs are the provider's statements. Confirm the identifier your account can call before changing a configuration.

  • Claude model deprecations ↗

    Lifecycle status, retirement dates and recommended replacements for Claude models and deprecated request parameters.

    Public documentation. Its dates apply to Anthropic-operated platforms; partner platforms set their own schedules. Requests to a retired model fail. Test the recommended replacement on your own workload before the retirement date.

  • OpenAI API pricing ↗

    Provider prices by model and processing mode, including cached input, built-in tools, audio and image generation.

    Public pricing documentation. No paid model call is made by this collection. A calculated estimate is not an invoice. Recheck the exact model, processing mode, region and effective date.

  • OpenAI API deprecations ↗

    Announced retirements of OpenAI models and endpoints, with shutdown dates and recommended replacements.

    Public documentation. Notice periods differ by model type, and preview models can be retired with much shorter notice. A recommended replacement is the provider's suggestion, not a measured equivalent. Test it on your own task before the shutdown date.

  • Gemini API pricing ↗

    Free and paid tier prices for Gemini API models, including context caching, batch processing and search grounding.

    Public pricing documentation. An automated reader that does not keep cookies may be sent to a sign-in page instead. The page says free-tier content is used to improve Google products and paid-tier content is not. Confirm the tier and its data terms before sending private material.

  • Gemini API deprecations ↗

    Gemini API models with release dates, shutdown dates and recommended replacements.

    Public documentation for the Gemini API. Check the schedule of any other Google platform you use separately. A replacement model can differ in price, limits and behavior. Measure it on the same test set before the shutdown date.

  • OpenRouter models API ↗

    An endpoint listing models available through OpenRouter with per-token prices, context length, supported parameters and modalities.

    Follow the documented authentication and request limits. A listing shows routing availability, not access through your own provider accounts. One model can be served by several providers at different prices and limits. Record the provider, price basis and retrieval date with any figure.

  • Artificial Analysis methodology ↗

    Definitions behind reported model quality, inference speed and price comparisons.

    Read the methodology and linked measurements; automated access or republication needs its own terms review. Keep the provider, endpoint, test configuration and measurement date with any cited result.

When to look again

When a provider announces a price change, model release or retirement, and before each budget review.

Give your agent this question

Check the named providers for price changes, new models and retirement notices that affect the current configuration. Cite each provider page with the date it was read, keep listed prices separate from observed invoices, and propose a side-by-side test before any switch.