Skip to main content

Methodology

How we measure AI models

This page explains how our indexes and own tests are built, where the data comes from and how current it is. It also lists the RSS feeds and charts you may reuse with attribution.
Test series in the overall index
84
Models with an overall value
115
Datasets observed
24
Newest data date
November 12, 2026

What we measure

Every index and test at a glance: which question it answers, where you see it and where the data comes from.
  • External data

    Overall index (Gradually Meta-Score v5)

    How strong is a language model compared with the others when many independent benchmarks are put together?

    Shown here:
    LLM comparison
    Data from:
    Independent evaluators and official leaderboards
    Go to section
  • External data

    LLM price index

    What does API use of language models cost in the market, and how has that developed?

    Shown here:
    LLM price index
    Data from:
    Developer price lists, model routers and API catalogs
    Go to section
  • External data

    Model popularity

    How many people search for, use and discuss a model?

    Shown here:
    AI trends
    Data from:
    Search volume, usage data and mentions
    Go to section
  • External data

    Vendor popularity

    How in demand is a vendor overall, regardless of how many models it has?

    Shown here:
    AI trends
    Data from:
    Search for the brand, usage of the models, mentions
    Go to section
  • External data

    Speed

    How many tokens per second does a model output?

    Shown here:
    LLM comparison
    Data from:
    Artificial Analysis
    Go to section
  • External data

    Cost per task

    What does it cost to solve a task of the Vals Index?

    Shown here:
    LLM comparison
    Data from:
    Vals AI
    Go to section
  • Own test

    SVG short test and model tests

    What does the same task look like with different models?

    Shown here:
    Model profiles
    Data from:
    Own test, one attempt per model
    Go to section
  • Own test

    GraduallyBench Image v2

    Which image model produces the better images for the same four tasks?

    Data from:
    Own test, rated by two AI judges
    Go to section
  • Own test

    GraduallyBench Decision, STT and TTS

    How well do models decide, how well do they recognize speech and how accurately does their speech output reproduce a text?

    Data from:
    Own test, evaluated automatically
    Go to section

Overall index of LLMs

How the overall value is built, how to read it and where it reaches its limits.

What the index answers and what it does not

The overall index summarizes how a language model performs in independent benchmarks. It answers one question: how strong is a model compared with the others when many tests from many areas are put together?

What it does not answer: it does not measure how many people use a model, which is what the popularity index is for. It does not tell you which model is best for your task either. A model with a lower overall value can lead for your use case. And it is not a probability of success.

Which measurements count

Right now 3,642 measurements from 84 test series go in. 115 models have an overall value, 95 of them a place. A test series is one benchmark that several models have taken.

  • Only independent evaluators and official leaderboards count. A number from the maker's own model card does not go in.
  • Only each source's current listing counts. Older retrievals do not replace a newer series.
  • For each source and benchmark one test setup counts, the one in which the most models are clearly matched. There is no picking of the best setup per model.
  • If a model has several configurations in the same benchmark, the one with the highest documented reasoning effort counts. The result never decides the selection.
  • A series needs at least 5 models.
  • Composite indices from other providers do not count on top of their individual tests, so nothing goes in twice.

How the values are combined

  • Each series is brought to a common scale: a value counts by how far it lies above or below the average of its series. Percentages are stretched so that the gap between 95 and 98 percent counts for more than the gap between 50 and 53.
  • From all series the index estimates one common strength for each model. Series that separate strong and weak models well count for more.
  • If a model has only a few test series so far, the index pulls its strength slightly towards the middle. That way a single outlier does not lift a new model straight to the top. Since version 5 this pull is weaker: a model with 8 test series lands on average where it would stand with all series, instead of about 1.5 to 2 points below as up to version 4.
  • On top of that comes one deviation per area from the common strength. If a model has only a few measurements in an area, the deviation is pulled towards zero. The areas are coding, reasoning, math, knowledge, agents, general tasks and multimodal tasks (core areas) and finance, law and health.
  • The overall value weights the 7 core areas with 75% and the 3 other areas together with 25%. An area without a measurement of its own counts with the model's common strength, not as zero.

How to read the number

Value
100 is the average of a fixed reference group of models. A gap of 15 points means the higher model comes out ahead in roughly three of four head-to-head comparisons in a typical benchmark. The scale is open at both ends and is not a percentage.
Place
The position among all models with a place, sorted by overall value. A model gets a place only when its value is certain enough: the uncertainty may be at most 7.35 points. Otherwise the value is shown as provisional. A model that already has a place keeps it up to an uncertainty of 7.65 points, so small fluctuations of the calculation do not shift places.
Performance groups
The top group (3 models) contains the winner and the models that are level with it. Then come the upper group from 115 points (7 models), the middle group from 85 points (41) and below it the lower group (44).
Level
A model is level with the winner if it lands ahead of it in at least 5% of the recalculations. If the winner is the same as in the newest index state, models already in that top group remain level down to 3.5%, while a new model joins only from 6.5%. For this the index recalculates 1,000 times, each time letting test families count several times or not at all at random.
Win chance
The share of those recalculations in which a model is in first place. The win chances of one area add up to at most 100%.

When a model gets no value or only a provisional one

An overall value needs at least 8 test series, 2 sources and 3 areas with measurements of their own. If any of these is missing, there is no value. That is a gap, not a zero.

Models that lack only the second source show a provisional value, always labelled “one source” (18 models). They get no place, no group and no win chance, and they do not move the scale.

Models without an independent overall value can get an estimate from vendor figures. It is shown separately and never goes into the index. It appears only when enough models are available to calibrate it and the estimate reproduces their order well enough.

Limits of the index

Vals AI supplies 58% of all observations in the index. If the index is recalculated without this source, Claude Opus 5.5 leads instead of Claude Fable 5.2.

The top therefore depends on a single source. Read it as a hint, not a verdict.

  • Models with few measurements carry more uncertainty. New models therefore often get a place only after a few more tests, and their value can still move by several points until then.
  • On average the vendor estimate lies about 10 points away from the independent value, so it is only a rough guide. For the models it rates highest the vendor estimate comes out slightly too low. That difference is not large enough to count as established.
  • Each series uses the highest documented reasoning effort. Some top models are measured only up to a lower effort, so the index partly compares compute too. The charts mark this.
  • Benchmarks measure tasks that someone picked. Your task may look different.

Versions and data

  1. Version 1October 19, 2026

    Rank percentiles, every area weighted equally.

  2. Version 2October 20, 2026

    Fixed editorial weights per area and test family.

  3. Version 3October 20, 2026

    Statistical model with one common strength per model, recalculations instead of fixed tie limits.

  4. Version 4November 4, 2026

    Scale with 100 as the mean and 15 points as the spread, unmeasured areas treated as unknown, evaluation with held-out test families.

  5. Additions in version 4November 10, 2026

    More recalculations, performance groups, a note on the share of the largest source and provisional values for models with a single source.

  6. Version 5November 11, 2026

    A weaker pull towards the middle for models with few test series. The limit for a place stays the same in points. Values from versions 4 and 5 are not directly comparable.

  7. Additions in version 5November 11, 2026

    A place and a seat in the top group are no longer lost through small fluctuations of the calculation. The vendor estimate pulls towards the middle as strongly as it did up to version 4 again.

The newest measurement in the index is from November 12, 2026.

More indexes

Prices, popularity, speed and cost per task. Each index answers its own question, and the values are not comparable with each other.

LLM price index

The price index makes API prices comparable. It includes publicly priced text and code models that are available through an active API from their developer or an API provider. Discontinued, specialized and legacy models are left out.

  • Prices come from several source systems: official developer prices, model router tariffs and independent API catalogs. Community catalogs serve as a cross-check.
  • Two separate runs a day reload the input and output prices and recalculate the whole index. It is published only when the price of every selected model is present and all checks have passed.
  • Input and output price form a blended price, by default 75% input and 25% output. The index is the popularity-weighted geometric mean of these blended prices.
  • The first historical checkpoint on September 1, 2022 equals 100 index points. A value of 50 means the price level is only half as high as then.
  • The price bands follow the displayed price per 1 million tokens: up to $1 low, over $1 to $5 medium, over $5 high.

The index is a market comparison, not an invoice amount. Caching, batch processing, discounts, per-request fees, taxes and self-hosted models are not included.

Model popularity index

The popularity score shows how many people search for, use and discuss a model. It runs from 0 to 100 and each area has its own scale. Scores compare within one area, not across areas.

  • Search counts for 54%, usage for 36% (for example API tokens, downloads or installs) and mentions in news and newsletters for 10%.
  • Only channels with a value count. When a channel is missing, its weight is spread over the others. A missing value is unknown and never 0.
  • Mentions enter as the mean of the last 30 days, search volume as a monthly value. A model with mentions only does not get a value yet.
  • A trend counts as “Rising” from +4 points against about four weeks earlier and “Rising fast” from +10. “New” marks rising models that are at most 14 days old.
  • Harnesses and AI plans use the same weights. For the best-known people in the industry, Wikipedia views count for 70% and mentions in newsletters and feeds for 30%.

In the LLM comparison you can switch the value between World, EU and Germany. Regionally only search and attention count, because there is no regional source for usage.

Popular does not mean good. When the method changes, for example through new data sources or a new scale, a value can jump. The timelines of the model profiles mark such changes, and they are no market event.

  • AI trends

    the most popular models, vendors, harnesses and AI plans

Vendor popularity

For vendors we collect our own signals. Simply adding up the model scores would measure the popularity of single models and favor vendors with many models.

  • Search (54%): the worldwide monthly search volume for the vendor, including its AI brand, such as ChatGPT for OpenAI. Per month the strongest spelling counts, spellings are never added.
  • Usage (36%): the vendor's tokens on OpenRouter and the downloads of its models on Hugging Face, weighted equally.
  • Attention (10%): the share of stories in a fixed public sample of RSS feeds and Hacker News that name the vendor, as the mean of the last 30 days.
  • Each channel is mapped to 0 to 100. When a channel is missing, only the others count. A missing channel is unknown and never 0.

Downloads are not a user count, and tokens on OpenRouter show only part of the market. Here too, popular does not mean good.

Speed

Speed is not a measurement of our own. The values come from Artificial Analysis and state output tokens per second. Where no current measurement exists, the value stays empty.

Cost per task

The chart “Performance vs. cost per task” sets the overall index against the cost Vals AI paid per task of the Vals Index, at the reasoning tier stated for each model. Higher tiers cost more because the model thinks for longer. The cost axis is logarithmic.

Own tests

Here we test models ourselves. These tests do not count toward the overall index and produce no overall ranking.

SVG short test and model tests

The SVG short test is a single task: the model draws a pelican riding a bicycle as an SVG. Every model gets the same prompt with the same fixed settings, without reasoning and with one attempt per model. You see the result on the model profiles and in the duels under “in our own test”.

  • The result is an impression, not a score. Identical test conditions do not make the models' internal compute identical.
  • Under each image you see the date of the test run, the response time and the cost of the attempt. All further details sit behind “Test details”.
  • Models for which we cannot confirm that reasoning was off are not shown as a comparable result. If the API request fails, the model is not evaluated.
  • We never mix results from different test rounds. If a selection has no shared round, we show no results.

On top of that come the “Our tests” on the model profiles with three tasks: a pelican on a bicycle, balls in a spinning heptagon and an animated solar system. We show the latest attempt without fixes. A successful recording proves neither correct physics nor a complete implementation of the prompt, and a single test gives no overall verdict on a model.

Image and video tests

GraduallyBench Image v2 is our own image test. Every model gets the same four tasks. Two AI judges compare the images in pairs and blind. That yields points from 0 to 100 per task, and the overall value is the mean of the four fixed tasks.

  • One image per model counts for each task. The ranking therefore rests on one attempt and stays separate from research benchmarks and the blind votes of the arenas.
  • Models that still lack tasks or the shared rating get no place.
  • Next to our test, the image model comparison shows the ratings from the anonymous LMArena blind comparisons.

For video models we show sample clips and the ratings from arena blind votes. We do not give videos a score of our own.

Decisions and audio

The category pages for decision and audio models show three automatically evaluated tests. They are pilot protocols, give no overall ranking and apply only to the exact tested model identifier and route. Every tested model carries its status, for example “Benchmark run”, “Partially tested”, “Technical test” or “Short functional test”.

GraduallyBench Decision v1
60 test cases from 30 scenarios in German and English. Five equally weighted task families (triage, routing, selection with constraints, numbers and tables, sufficient evidence) form a score from 0 to 100. Failed requests and invalid answers count as unsuccessful. Robustness variants and development cases are reported separately.
GraduallyBench STT v1
Speech recognition on 32 read-speech recordings in German and English with four speakers each, plus four digital-silence clips. We measure word error rate (WER) and character error rate (CER), and for silence the invented words. Spontaneous speech and background noise are outside the test.
GraduallyBench TTS v1
The model speaks a text, a recognition model transcribes the recording back, and we compare the return text with the input text. That measures how accurately the content arrives, not how natural a voice sounds.

The reference answers follow stored rules and source transcripts. Task wording, translations and transcripts have not been checked by humans.

Data status

Prices, popularity, benchmarks and directories come from automatic jobs. Here you can see the date of every dataset and whether it is on schedule.

Every dataset at a glance

This page is rebuilt with every release. The status applies to the moment of the check: November 12, 2026 at 01:32 PM. The current state comes from the live endpoint: Data status as JSON.

Prices

  • LLM price index
    Price index, price history and model prices
    November 11, 2026Late
    Rhythm: twice daily. Produced by: Cloud price job
  • Task costs in the price index
    Cost per solved benchmark task
    November 11, 2026Late
    Rhythm: twice daily. Produced by: Cloud price job

Popularity

  • Model popularity (scores)
    Popularity scores of the models and their history
    November 9, 2026 at 04:21 AMStale
    Rhythm: daily. Produced by: Cloud directory job
  • Model popularity (weekly values)
    Weekly values in the popularity charts
    November 9, 2026Stale
    Rhythm: daily. Produced by: Cloud directory job
  • Model trends
    The “Trending now” list
    November 1, 2026Stale
    Rhythm: daily. Produced by: Cloud directory job
  • Vendor popularity
    Popularity of the vendors
    November 9, 2026 at 04:26 AMStale
    Rhythm: daily. Produced by: Cloud directory job
  • Harness and subscription popularity
    Popularity of the harnesses and plans
    November 9, 2026 at 04:25 AMStale
    Rhythm: daily. Produced by: Cloud directory job
  • AI people popularity
    Ranking of the best-known people in AI
    November 9, 2026 at 04:26 AMStale
    Rhythm: daily. Produced by: Cloud directory job

Directories

  • Skills directory
    Claude Code Skills and Codex Skills
    November 9, 2026 at 04:03 AMStale
    Rhythm: daily. Produced by: Cloud directory job
  • Plugin directory
    Claude Code plugins
    November 9, 2026 at 04:03 AMStale
    Rhythm: daily. Produced by: Cloud directory job
  • MCP directory
    MCP servers with stars and activity (latest metadata check)
    November 9, 2026 at 04:02 AMStale
    Rhythm: daily. Produced by: Cloud directory job
  • Changelogs
    Changelogs of the AI tools
    November 9, 2026 at 04:02 AMStale
    Rhythm: daily. Produced by: Cloud directory job

Benchmarks and speed

  • OpenRouter speed
    Output speed of the language models
    no dateNot active yet
    Rhythm: daily. Produced by: Cloud directory job
  • Benchmark database
    Overall index, area values and all model benchmark tables
    November 12, 2026Current
    Rhythm: daily. Produced by: Codex task on the Mac
  • Overall index history
    History of each model's overall index value
    November 12, 2026Current
    Rhythm: daily. Produced by: Codex task on the Mac
  • Artificial Analysis speed snapshot
    Historical and supplementary speed values
    November 12, 2026Current
    Rhythm: daily. Produced by: Codex task on the Mac
  • Image model ranking (LMArena)
    Arena ratings of the image models
    November 10, 2026Late
    Rhythm: daily. Produced by: Codex task on the Mac
  • Video model ranking (LMArena)
    Arena ratings of the video models
    November 5, 2026Stale
    Rhythm: several times a week. Produced by: Codex task on the Mac

Search data for comparisons

  • Comparison pair popularity
    Order of the recommended comparisons
    November 10, 2026 at 06:55 AMLate
    Rhythm: daily. Produced by: Mac job
  • Search demand for comparisons
    Decides which comparison pages are indexed
    November 11, 2026Current
    Rhythm: daily. Produced by: Mac job
  • Search demand for model profiles
    Decides which model profiles are indexed
    November 11, 2026Current
    Rhythm: daily. Produced by: Mac job

Catalogs

  • AI subscription catalog
    Plans, prices and included models in the subscription comparison
    November 10, 2026Late
    Rhythm: daily. Produced by: Codex task on the Mac
  • Harness development data
    Releases, repository activity and packages of the harnesses (maintained by hand)
    November 5, 2026 at 11:53 PMCurrent
    Rhythm: by hand, about every two weeks. Produced by: by hand
  • Open-source LLM directory
    Directory of open language models and the hardware check (maintained by hand)
    October 27, 2026Older than usual
    Rhythm: by hand, about every two weeks. Produced by: by hand

What the statuses mean

Current
The data date is within the usual rhythm.
Late
The latest run was delayed, the next one is still due.
Stale
At least one scheduled run did not happen.
Unknown
The dataset carries no readable date.
Not active yet
The dataset is not switched on yet and counts as neither late nor stale.

Where the data comes from

Prices

The LLM price index reads the vendor pages and several price directories twice a day. If a run fails, the price index date shows it right away.

Popularity

The values come from search volume, usage data and mentions in public sources. A daily run recalculates them, and weekly values and trends are derived from them.

Directories

Skills, plugins, MCP servers and changelogs are updated daily from the vendors' public sources and from GitHub. For the MCP directory, the latest metadata check counts.

Benchmarks and speed

Benchmark values, speed measurements and arena ratings are compared daily with the published results of independent tests and the vendors.

Search data for comparisons

Google Search Console data decides which comparisons appear as popular and which comparison and profile pages should show up in search.

Catalogs

The subscription catalog is checked daily. The harness development data and the open-source directory are maintained by hand, so a higher age is normal there.

Open data

RSS feeds to follow and charts for your own site.

RSS feeds

Three feeds report changes as soon as they are confirmed. Paste the address into your feed reader.
  • AI models: price changes

    Confirmed API price changes from the Gradually LLM Price Index.

    https://www.gradually.ai/en/feeds/price-changes.xml

  • AI models: new releases

    New AI models of the last 14 days with a sourced release date.

    https://www.gradually.ai/en/feeds/new-models.xml

  • AI graveyard: shutdowns

    Announced and confirmed shutdowns from the AI graveyard.

    https://www.gradually.ai/en/feeds/shutdowns.xml

Charts to embed

The charts adapt to the width and update with our data. You copy the code below each chart.
  • The best LLMs in the overall index

    Recommended height: 760 pixels

    View chart
    Embed this chart

    Paste the code into your page. The chart adapts to the width and updates with our data.

    You may use the chart with attribution (CC BY 4.0).

  • Gradually LLM Price Index

    Recommended height: 500 pixels

    View chart
    Embed this chart

    Paste the code into your page. The chart adapts to the width and updates with our data.

    You may use the chart with attribution (CC BY 4.0).

  • The most popular AI models

    Recommended height: 820 pixels

    View chart
    Embed this chart

    Paste the code into your page. The chart adapts to the width and updates with our data.

    You may use the chart with attribution (CC BY 4.0).

Use and cite

Name the source whenever you use the data. The matching line for each chart is listed below.

You may use all charts with attribution (CC BY 4.0). CC BY 4.0

Attribution

  • Source: gradually.ai, https://www.gradually.ai/en/llm-comparison/
  • Source: gradually.ai, https://www.gradually.ai/en/llm-price-index/
  • Source: gradually.ai, https://www.gradually.ai/en/ai-trends/