Unverified50% confidenceFactExact time
Mainstream large-model APIs bill by input tokens and do not retain server-side session state, causing the same log segment to be counted as input tokens again in subsequent turns.
1
Sources
50%
Confidence
Long-term
Relevance
10/18/2026
First Seen
Sources
Related Entities
Related Claims
VerifiedMainstream large model APIs charge separately for input tokens and output tokens, with input tokens typically including the entire conversation history (i.e., the context).80% similarUnverifiedAPI billing typically distinguishes between input tokens and output tokens; in multi-turn conversations, the outputs from earlier turns become inputs in later turns and are billed again.78% similarUnverifiedAutomatic prompt tuning consumes a large number of tokens in the model's back-and-forth self-correction process, incurring additional API call, token, and latency overhead.75% similarUnverifiedMainstream model APIs charge separately for input tokens and output tokens, where input includes system prompts, context history, and retrieved document fragments74% similarVerifiedAPI billing covers both input tokens and output tokens, and as a conversation extends, the input tokens carried in each request grow linearly.74% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1060028API
curl https://kongchang.com/api/v1/knowledge/claims/1060028MCP
get_claim(id=1060028)