Unverified50% confidenceFactExact time
The API is stateless and does not remember the system prompt between calls, so each request must resend it and pay for it again.
1
Sources
50%
Confidence
Long-term
Relevance
10/19/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedWhen the API is unavailable, applications should implement graceful degradation by returning cached results, prompting users to retry, or switching to a fallback solution, rather than crashing directly71% similarUnverifiedAPI Keys are designed with no concept of expiration and remain valid long-term once generated; whereas tokens have an expiration time and require re-login to obtain after expiry.69% similarUnverifiedModifying the system prompt to adjust effort invalidates the prompt cache; the official recommendation is to control effort via API parameters rather than prompt text in order to maintain cache validity.66% 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.66% similarUnverifiedOnly 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.65% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1067108API
curl https://kongchang.com/api/v1/knowledge/claims/1067108MCP
get_claim(id=1067108)