Models410
With endpoints119the other 291 render “— · not in snapshot”
Endpoint rows365
Providers72serving, of 103 registered
ZDR rows6the only zero-data-retention evidence in the data
Benchmarks158models carrying an Artificial Analysis block
Latency rows0of 365 endpoint rows carry a reading; the rest render blank
From the APImodel id, name, description, context window, max output, modalities, supported parameters, release date, knowledge cutoff, moderation flag, catalogue pricing, per-endpoint pricing, endpoint discount, provider identity, routing tag, quantization, context ceiling, implicit caching, uptime, policy documents, headquarters and datacenters, latency, throughput, Intelligence index, Coding index, Agentic index, Design Arena ELO, region and zero-data-retention.
Blank herelatency and throughput. The spec exposes these only to an authenticated caller, so they are not absent upstream — our capture was taken without a key and nothing on this deployment has reported one yet. Every cell is an em-dash, and the sorts that would need them are disabled rather than quietly reordering by another key.
Blank on this deploymenttoken volume, request counts, trend series and popularity ordering. No field for any of them exists in the API contract. Nothing has been metered through this gateway yet, so every one of them is blank.
Not in the API at allProvider availability for a model with no endpoint row, training policy, retention window, BYOK, uptime history, blended or cache-adjusted pricing, and app attribution. None of these has a field to read, so none is claimed: they render “— · not in snapshot” or “Unknown”. Zero-data-retention is the one nearby exception — it is shown only where a routing tag carries a literal zdr segment, and is “Unknown” everywhere else.