Skip to contentSkip to results
Alpha Data may be incomplete — we’re still collecting and structuring it.

Methodology

What each kind of record must show before it is published, how it is compared or ranked, and which sources in the public register feed it.

Evidence statuses

Every fact carries one of six statuses. The status says how far the fact is checked; it is not a rating of the product.

Checked against an official or independent source.
Stated by the developer or provider and not independently checked.
Derived by the editors from other recorded values; the derivation is shown with it.
Another source contradicts it. Both are kept, and it is not ranked until an editor resolves it.
No source reports it. It is written out as unknown and never shown as zero.
Not rechecked within the expected time; shown with the date of the last check.

Importance in the feed

“Important” orders events by the importance the editors record when they publish an event — high, medium or low — and then by publication time. Importance is about the effect on readers, such as a critical advisory or a price change; it is not a measure of attention.

“Latest” shows events by publication time only. Updates to existing events are shown apart from new events.

Sources in the register

Calculated from published records, not read from a separate source.

Open the event feed

Pricing

Every price names the exact offer: the provider, the model version or plan, the billing unit, the tier, the region and the date it took effect.

  • A price not rechecked for 14 days is shown as last known, with its date.
  • A promotional price is marked as such. A price on request stays “On request”: it is never estimated or averaged.
  • The calculator uses the published prices of the offers you choose; a missing price blocks the exact total instead of being guessed.

Comparisons

Only like is compared with like: model versions with model versions, agents with agents, tools with tools of the same type. A model is never compared with an agent.

An unknown value never counts as a match or as a difference. “Best” is marked only between direct alternatives, and only when one value is strictly better.

Sources in the register

Calculated from published records, not read from a separate source.

Open the comparison

Benchmarks

A score is shown with the benchmark version, the unit, the harness, the snapshot and the run date. There is no overall winner across benchmarks.

  • Only published results in a comparable cohort get a place.
  • A developer's claim without a published source is shown apart and is not ranked.
  • A run with a different harness, prompt budget or benchmark version is excluded from the ranking, with the reason.
  • Price-performance uses the lowest published API input price of the same model version and is shown with its formula.
Open the benchmarks

Open source

Open weights, open source code and commercial use are three separate facts. A licence is shown with what it covers and what it says about commercial use; “Not stated” is never read as permission.

Hardware estimates use the stated parameter count at 16, 8 and 4 bits. Links go to the publisher's page or repository, never to a download.

Open Open Source Radar

Research

Bibliographic data is kept apart from the editors' reading. Why a paper was selected and what is new in it are editorial judgement, labelled as such, never a score.

Peer review is taken from the publisher's record: a preprint or “Not reported” is never counted as peer-reviewed. An authors' revision is a new version of the paper, not a correction.

Open research

Security

Each incident shows its severity as its source publishes it, the affected and fixed versions and the disclosure status. The editors do not re-score severity, and no CVSS score or CVE identifier is invented.

No record of an incident is not a safety rating. A missing fix date does not mean the issue is fixed, and embargoed details stay hidden until the embargo ends.

Open security incidents

Compatibility

A check names the product version and the protocol version it covers and fills only that cell of the matrix. Each cell is Supported, Partial, Not supported or Not checked, with its basis and evidence.

A developer's own listing is “Not checked”. A check older than 90 days is marked as possibly out of date.

Sources in the register

Each check cites its own source; the matrix shows it on every cell.

Open the compatibility matrix

Digests

An issue lists only stories reviewed and published in its period, each once, linking to its report. A day or week without a reviewed story has no issue; nothing is added to fill it.

A corrected issue says what changed and when, and keeps its original publication time.

Sources in the register

Calculated from published records, not read from a separate source.

Open the digests

Cookie settings

Necessary storage is always on. Choose whether to allow the optional categories.

Your privacy choices

Necessary storage keeps the site working. Analytics and advertising stay off unless you allow them. Cookie notice

Sections

PrivacyTermsCookies

© 2026 AI Frontier Index