Verified75% confidenceFactExact time
API 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.
3
Sources
75%
Confidence
Medium-term (~90 days)
Relevance
9/18/2026
First Seen
Valid until: 12/17/2026
Sources
Related Entities
Related Claims
UnverifiedMainstream 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.78% similarVerifiedAPI billing covers both input tokens and output tokens, and as a conversation extends, the input tokens carried in each request grow linearly.77% similarUnverifiedThe observation returned by any tool call permanently resides in the conversation context as tokens, and is re-read and billed in every subsequent round, so the more verbose the tool output, the higher its marginal cost.71% similarVerifiedMainstream large model APIs charge separately for input tokens and output tokens, with input tokens typically including the entire conversation history (i.e., the context).70% similarUnverifiedDuring multi-turn tool calls, each tool execution result is appended to the conversation history as a new tool_result message, and the model reads the outputs of previous steps from the conversation context rather than retaining intermediate values in internal memory.70% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/931943API
curl https://kongchang.com/api/v1/knowledge/claims/931943MCP
get_claim(id=931943)