Unverified50% confidenceDecision RuleExact time
The platform convention defines an idempotency key request header and provides a default 24-hour deduplication window; retries with the same key within 24 hours are recognized as duplicates, while beyond that they are treated as new requests; the client should generate the key before initiating the request and persist it, reusing the same key when retrying.
1
Sources
50%
Confidence
Long-term
Relevance
10/12/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedA common technique for achieving idempotency is for the client to generate a unique idempotency key sent with the request, while the server records the result associated with that key and returns the cached result upon receiving a duplicate request.64% similarUnverifiedAfter applying for two free API keys, the tool can be run locally within minutes.64% similarUnverifiedThe relay service supports revoking an API key and regenerating it with a single click at any time.64% similarUnverified应为每个请求设置工具调用次数、耗时和花费上限,触及上限时必须产生明确交接而非编造结果63% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1011711API
curl https://kongchang.com/api/v1/knowledge/claims/1011711MCP
get_claim(id=1011711)