Measured inference.
With context.

03 / Methodology & limitations

Population, not adoption

One observation per correlated usage record for this model. Requests—not users—are weighted equally. Operator traffic may be present, and a few accounts may dominate. Caller-identified synthetic traffic is excluded; unlabeled historical probes cannot be reliably separated. These are not customer counts.

Successful streaming requests only

Timing and speed require successful usage and gateway outcomes, no client abort, more than one generated token, a positive observed output window, and valid duration. Non-streaming, failed, cancelled, single-token, and uncorrelated requests are excluded. Coverage uses successful usage records as its denominator—not all incoming API attempts. This is not an error-rate or uptime report.

Timing boundaries

Exact timings use a monotonic clock from gateway arrival, including account queueing, to observed upstream output. First output includes reasoning and tool events; first answer requires answer text. Client network travel and rendering are excluded. Historical estimates subtract the output-stream window from total duration and include the post-output tail.

Speed and token accounting

End-to-end speed divides generated tokens by the entire gateway duration, including the initial wait. It includes reasoning tokens and is not decode-only throughput. Cache and reasoning counters are recorded only when reported, not inferred as zero. In this measured cohort, cache counters are available for 30 requests and reasoning counters for 27.

Sample thresholds and missing hours

Medians require 20 samples; p95 requires 100, independently for each metric and bucket. These publication thresholds are not statistical confidence guarantees. Missing results stay blank. p95 means 95% of measured timings were at or below that value. No interpolation or synthetic gap filling.

What this does not establish

Observed performance depends on request mix, cache reuse, reasoning, and shared load. It does not establish coding quality, fleet capacity, availability, an SLA, or the speed your next request will receive. See service status for monitoring information.