Unverified50% confidenceOpinionExact time
Requests that hit the cache should not be billed twice, and retries generated by failover should be attributed to the team of the original request.
1
Sources
50%
Confidence
Long-term
Relevance
10/24/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedOnly operations that have no side effects on system state or produce consistent results when executed repeatedly (such as GET requests and write operations with idempotency keys) should be automatically retried; blindly retrying ordinary POST creation requests may lead to duplicate resource creation.70% similarUnverifiedWhen encountering rate-limiting errors, one should not continuously retry to reset the window; staggering request times allows for continued usage.69% similarUnverifiedThe API is stateless and does not remember the system prompt between calls, so each request must resend it and pay for it again.67% similarUnverified切换应用时前端可能重新初始化会话状态，触发新的查询请求，而旧请求未被正确取消导致重复计费，这是一种竞态条件问题67% similarUnverifiedIn the cache reuse mechanism, once the request prefix is modified, the cache for all content after it becomes invalid; modifying tools or other parts of the request will still affect reuse.67% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1092869API
curl https://kongchang.com/api/v1/knowledge/claims/1092869MCP
get_claim(id=1092869)