Skip to main content
The model catalog is generated from GET /models every hour. This page explains how the numbers on it are derived, so you can reproduce them and know what they do and don’t mean.

Families and variants

Many model IDs are the same model offered in a different way. The catalog groups them into one family page: Every variant keeps its own model ID, price and privacy tier. Pass the variant’s ID as model. Dated snapshots such as deepseek-v4-flash-0731 stay separate families and appear under Other versions. An E2EE build, such as e2ee-glm-5-3-p for z-ai-glm-5-3, has a page of its own rather than being a variant: calling it takes the E2EE handshake, and its limits and price differ. Its page is named for its model plus E2EE, at the model’s URL plus -e2ee, and each of the two pages links to the other.

Normalized prices

Each modality bills in its own unit. The catalog shows the native unit and one reference price, so models can be sorted and compared.
Reasoning models can spend many more output tokens than non-reasoning models on the same task, so the blended price understates their real cost. Cost per task, measured on benchmark runs, is planned; see Benchmarks.

Video pricing

Video models don’t publish prices in GET /models. At build time, Venice calls POST /video/quote for every resolution × duration × audio combination each model supports, at its first listed aspect ratio (aspect ratio does not change the price). The catalog stores the full matrix and derives:
  • Per second: the median of price ÷ seconds across durations at a given resolution and audio setting. Prices are linear in duration for almost every model.
  • Draft clip: 5 seconds, 720p, silent.
  • Production clip: 10 seconds, 1080p, with audio.
When a model doesn’t offer the requested setting, the catalog uses the closest one it supports and marks the price. Edit, motion-control and upscale modes bill by the length of your source video, so they show By source instead of a price. Always call POST /video/quote before queueing for an exact amount.

Privacy tiers

A family lists every tier its variants offer. Filtering by a tier shows the variant in that tier, with its own price.

Reference prompt suite

Image and video models are rendered on a fixed prompt suite, the same prompts for every model of a modality, at default settings. That’s what keeps the explorer’s gallery comparable from one model to the next. Most renders come from the model pages on venice.ai. Where venice.ai has none, the docs render the same suite through the Venice API, with video models on the cinematic landscape prompt only, to keep the clips light. Models without renders are listed under No reference renders yet.

Performance

Text model pages show time to first token, output speed and uptime for the last 24 hours, measured on Venice traffic from the API, venice.ai and the app. The figures are counts and timings of requests, never their prompts or outputs. They’re refreshed every hour, and a page stops showing them once they’re more than six hours old. A figure needs 20 requests for time to first token and output speed, and 100 for uptime. Below that, its card is left out, and a model without any figures has no performance cards. Time to first token and output speed charts split the 24 hours into equal periods of 15 minutes, 1 hour, 3 hours, 6 hours or the whole day: the shortest length at which every period with requests has as many as the day’s figure needs. Every point is then a real figure on enough traffic, and a model with little of it gets a few long periods, or one flat line at its daily figure. A period without requests, such as before a new model’s first, leaves a gap in the line. A model whose periods are longer than an hour shows where its figure falls among the other text models in place of a line, further right being better. They put the median period halfway up and draw anything over twice the median at the top, and hovering or dragging gives each period’s figure. Uptime charts give each quarter hour of the day two thin bars: green when it was up, the warning color when degraded (under 95%), red when down (under 80%), and grey when it had no requests, such as before a new model’s first. Below 100 requests, a quarter hour only reads as degraded or down when even the optimistic end of its 95% Wilson interval is under the line, so one failure among a few requests stays green. Hovering or dragging gives each quarter hour’s uptime. Below 100 requests, a quarter hour with a failure gives its status instead, since its uptime could give away how many requests it had. On a model whose quarter hours without requests are scattered over more than an eighth of the day, they shrink to a thin line. Under each figure, time to first token and output speed say where the model ranks among the other text models, and uptime how long it was down or degraded. The page’s Compare table gives time to first token and output speed for similar models.

Planned

Not published yet. This describes what the catalog will show.
Venice will measure the other modalities with synthetic probes, never customer prompts, and publish: Text models will also get time to a 500-token response and cache hit rate, which is cache_read ÷ (input + cache_read + cache_write) across all traffic.

Benchmarks

Text model pages show GPQA Diamond: 198 graduate-level questions in biology, chemistry and physics, four options each, run by Venice through the API on each model as Venice serves it.
  • Score. A model’s score is its run at its default reasoning, or its best run until it has one, and its rank counts every text model with a score. A run at another setting carries it in the name, as Artificial Analysis names configurations: Kimi K3 (off).
  • Price. Each chart plots every text model with a score against its blended price on Venice, three input tokens for each output token. The shaded corner holds the models that score higher for less; when it’s empty, no model on Venice beats this one on both.
  • Confidence. Each score has a 95% confidence interval, shown when you hover the score and published in the data, so models a few points apart are effectively tied.
  • Broken runs. A run that scores below chance, 25%, measured a broken setup and is left out.
Benchmarks are chosen for the frontier: still discriminative at the top, resistant to contamination, and runnable against the model as Venice serves it. Every score will carry one provenance label, never averaged together:
  • Venice-verified: run on the Venice endpoint shown on the page.
  • Independent: run by a third party, usually on the lab’s own API.
  • Lab-reported: published by the model’s creator.
Each score also shows the benchmark and harness version, reasoning effort, test date and a confidence interval. Scores older than 90 days, or superseded by a new benchmark version, are flagged as stale. The set is reviewed every quarter. A benchmark becomes a floor check, no longer a headline, once frontier models saturate it or it fails a contamination audit.

Machine-readable data

The catalog behind these pages is published as JSON at /data/model-catalog.json and rebuilt with every hourly sync. It suits comparison, analysis and agents; to pick a model at runtime, call GET /models. Fields without a value are left out. Prices are in USD. The performance figures are a separate file, /data/model-performance.json, also refreshed with every hourly sync: Venice’s own benchmark scores are a separate file as well, /data/model-benchmarks.json, which the hourly sync updates when a new run lands:

Data sources

The catalog is built from public endpoints you can call yourself: Prices are in USD. DIEM is billed at parity.