Unverified50% confidenceBenchmarkExact time
In the same test, under the default configuration the 36 successful requests caused the server to additionally reject 255 requests, a request amplification factor of 2.55x.
1
Sources
50%
Confidence
Long-term
Relevance
10/19/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedAPI request retries on streaming failures could reach as many as 21 times; non-streaming fallbacks now share the same retry budget as the original request.77% similarUnverifiedIn validation testing, the model refused all 27 requests for prohibited capabilities and all 23 requests for unsupported operations.76% similarUnverifiedIn a benchmark of 200 identical requests, connecting directly to the provider produced 200 upstream calls, whereas going through the proxy produced only 1 upstream call, with 199 requests joining the shared result, and the slowest response was still 1.58 seconds.76% similarUnverifiedOf the 35 denials, 33 were for the reason bad_or_unscoped_token, and one each was triggered by an unknown provider and the daily request cap.75% similarUnverifiedIn the benchmark's 60 runs, the early termination conditions were triggered 27 times, including 21 detections of lack of progress and 6 cases of model provider unavailability.71% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1064729API
curl https://kongchang.com/api/v1/knowledge/claims/1064729MCP
get_claim(id=1064729)