Unverified50% confidenceSolutionExact time
In streaming responses, the client may disconnect midway or stop reading, so cost recording should be placed in the finally block of try/finally rather than after the consumption loop, to ensure that early exits are also recorded.
1
Sources
50%
Confidence
Long-term
Relevance
10/13/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedFor disputes involving 'forgotten auto-renewal cancellation,' merchants can often provide records of user consent, so the chargeback success rate is not high and it should be used as a last resort.74% similarUnverifiedWhen a streaming response is interrupted midway, the portion of output tokens already generated is still billed, even though the client may not have received the complete result.71% similarUnverifiedToken consumption is paused while the watchdog waits—it is only polling API status and incurs no additional cost; failed retries, by contrast, may consume more tokens because the context is sent repeatedly.69% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1014561API
curl https://kongchang.com/api/v1/knowledge/claims/1014561MCP
get_claim(id=1014561)