Unverified50% confidenceFactExact time
If the bill is split at the moment the health check passes (386.7 seconds), startup appears to account for 60%; but the first user actually gets an answer at about 563 seconds, by which point 88% of the bill has already been consumed.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/12/2026
First Seen
Valid until: 1/10/2027
Sources
Related Entities
Related Claims
UnverifiedThe measured timeline was: billing starts at 0 seconds, prefill CUDA graph capture completes at about 371 seconds (taking 287.7 seconds), /health returns 200 at 386.7 seconds, the first request completes at about 563 seconds (taking about 176 seconds), the second request completes at about 579 seconds, and billing stops at 639.6 seconds.70% similarUnverifiedGoing from 4.1 seconds to 1.7 seconds represents a reduction in load time of approximately 58%.68% similarUnverifiedOn its first run, after backfilling history, the scorer identified 263 one-hour stalls and two eleven-hour stalls; on a second-pass check, agents were actually working during about 108 points' worth of one-hour waits and those points were refunded; the two eleven-hour stalls were kept (the audit role was idle from 08:47 to 19:46 while the queue piled up).68% similarUnverifiedThe per-attempt time figures of 19.2 minutes versus 37.0 minutes cited in the report are simulated estimates, not measured customer time savings.65% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1012427API
curl https://kongchang.com/api/v1/knowledge/claims/1012427MCP
get_claim(id=1012427)