Unverified50% confidenceDecision RuleExact time
Cut redundant tokens first, then enable caching: deleted tokens cost nothing, whereas cached tokens still cost a little on every call, and full price is paid when the cache expires.
1
Sources
50%
Confidence
Long-term
Relevance
10/19/2026
First Seen
Sources
Related Entities
Related Claims
VerifiedIn cache hit scenarios, hit tokens are typically charged at 1/10 of the original price or even lower78% similarUnverifiedPrompt Cache refers to a provider caching already-processed identical prefix tokens, where the price of cache-hit tokens is typically only 10%–50% of the normal price.72% similarUnverifiedCache hits reduce the billing rate per request, not the absolute amount of tokens consumed.72% similarUnverifiedThe cost of the fixed context can be approximated as: number of fixed-prefix tokens × number of calls × cache-read unit price.71% similarUnverifiedOverly long system prompts bring hidden overhead: for example, when the system prompt has 500 tokens while the actual input has only 50 tokens, it means 91% of the cost goes to boilerplate text; auditing and trimming the system prompt by 40% can reduce costs.71% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1067116API
curl https://kongchang.com/api/v1/knowledge/claims/1067116MCP
get_claim(id=1067116)