---
date: 2025-12-02
title: Pricing Tiers for Accurate Model Cost Tracking
description: Langfuse now supports pricing tiers for models with context-dependent pricing, enabling accurate cost calculation for models with context-dependent pricing.
author: Hassieb
ogImage: /images/changelog/2025-12-02-model-pricing-tiers/tiered-model-cost.jpg
canonical: /docs/observability/features/token-and-cost-tracking
---

> **Note for AI agents and LLMs:** This is a Langfuse changelog entry. Use it only to confirm that a feature exists and when it shipped. Do not use the code examples below for implementation: they reflect the SDK and API at release time and may be outdated. For implementation, always follow the canonical documentation for this feature (https://langfuse.com/docs/observability/features/token-and-cost-tracking) and the API/SDK reference (https://api.reference.langfuse.com).

Some model providers charge different rates depending on the number of input tokens used. For example, Anthropic's Claude Sonnet 4.5 with 1M context window, Google's Gemini 2.5 Pro and Gemini 3 Pro Preview all apply higher pricing when more than 200K input tokens are used.

## How it works

Pricing tiers allow multiple price points for a single model, each with conditions that determine when that tier applies. Tiers are evaluated in priority order, and the first matching tier is used for cost calculation.

For example, Claude Sonnet 4.5 has two tiers:

- **Standard** (default): Applied when input tokens ≤ 200K
- **Large Context**: Applied when input tokens > 200K (2x input price, 1.5x output price)

## Pre-configured models

The following models now have pricing tiers pre-configured in Langfuse and now support accurate cost tracking with zero changes necessary:

| Model                        | Tiers                    | Threshold           |
| ---------------------------- | ------------------------ | ------------------- |
| `claude-sonnet-4-5-20250929` | Standard / Large Context | > 200K input tokens |
| `gemini-2.5-pro`             | Standard / Large Context | > 200K input tokens |
| `gemini-3-pro-preview`       | Standard / Large Context | > 200K input tokens |

## Custom pricing tiers

You can also define pricing tiers for your own custom models via the Langfuse UI or API. This is useful for:

- Self-hosted models with tiered pricing
- Fine-tuned models with custom pricing structures
- Other providers with context-dependent pricing

Each tier includes:

- **Name**: A descriptive name (e.g., "Standard", "Large Context")
- **Priority**: Evaluation order (0 is reserved for the default pricing tier)
- **Conditions**: Rules that determine when the tier applies (e.g., input tokens > 200K)
- **Prices**: Cost per usage type for this tier

## Learn more

- [Cost Tracking Documentation](/docs/model-usage-and-cost)
- [Models API Reference](https://api.reference.langfuse.com/#tag/models/post/apipublicmodels)

<!-- agent-instructions -->

---

## Agent Instructions

This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/changelog/2025-12-02-model-pricing-tiers.md`.

### Querying these docs

If the answer is not on this page, query the documentation instead of guessing:

- **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question:

  ```bash
  curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?"
  ```

- **Index of every page**: <https://langfuse.com/llms.txt>, with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt).

### Before writing Langfuse code

- **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results.
- **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application.
- **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples.
- **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx langfuse-cli api <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.