Unverified50% confidenceFactExact time
Input token billing for the Decision API typically covers the user's incoming prompt and retrieved recall content, while output tokens correspond to the final result returned by the model.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/8/2026
First Seen
Valid until: 1/6/2027
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).76% similarUnverifiedtoken消耗的精确计量依赖于对Cursor官方API响应体中usage字段（包含prompt_tokens、completion_tokens）的实时解析75% similarUnverifiedLarge model services adopt a Token quota mechanism, where each model call consumes Tokens measured by the input and output text74% similarVerifiedAPI billing covers both input tokens and output tokens, and as a conversation extends, the input tokens carried in each request grow linearly.73% 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.67% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/987417API
curl https://kongchang.com/api/v1/knowledge/claims/987417MCP
get_claim(id=987417)