PulseAugur
EN
LIVE 03:03:34
Português(PT) Por que duas requisições de 1,4M tokens no Cursor custaram valores tão diferentes

Cursor LLM costs vary significantly due to token category pricing, not just volume

A user analyzing their Cursor application's LLM usage discovered that request costs are not solely determined by the total number of tokens. Two requests of nearly identical token count, 1.34 million and 1.40 million, had significantly different costs: $1.13 and $2.96, respectively. This discrepancy arises because LLM costs are calculated based on a weighted sum of four categories: input, cache write, cache read, and output, each with its own pricing. The first request in a session is typically the most expensive due to cache write costs, while subsequent requests benefit from cheaper cache reads. Changes within the context, such as editing rules or summarizing history, can invalidate the cache and lead to higher costs for subsequent tokens. AI

IMPACT Understanding LLM cost structures is crucial for optimizing AI application development and deployment.

RANK_REASON User-level analysis of a specific product's cost structure.

Read on dev.to — LLM tag →

AI-generated summary · Google Gemini · from 1 sources. How we write summaries →

Cursor LLM costs vary significantly due to token category pricing, not just volume

COVERAGE [1]

  1. dev.to — LLM tag TIER_1 Português(PT) · Quézia Balonecker ·

    Why did two 1.4M token requests on Cursor cost so different?

    <p>Outro dia, analisando o painel de uso do Cursor para entender para onde meus tokens estavam indo, parei em duas requisições que tinham acabado de rodar. O instinto é olhar a contagem de tokens e assumir que a maior foi a mais cara. Ao comparar as duas, não foi isso que encontr…