Methodology

Keep each claim close to its evidence.

The site uses a simple source hierarchy so a reader can see what is documented, what is independently measured, and what remains a reasoned recommendation.

01 / Primary sources

Provider documentation establishes release and API facts.

Release notes, model lists, and pricing documentation are used for model identifiers, stated capabilities, availability, and commercial terms. Live documents take precedence over this static site.

02 / Independent sources

Trackers provide context, not proof of a vendor claim.

Independent indexes and benchmarks can be useful when their model route, date, setup, and measurement scope are clear. They are labeled separately from provider information.

03 / Community reports

Practitioner experience is a test lead, not a verdict.

Community discussion can reveal workflow fit and failure modes. It is never treated as a controlled benchmark or substituted for a team’s own evaluation.

04 / Comparisons

Compare conditions before comparing headlines.

Pricing units, context windows, input modalities, availability, and test configurations are disclosed where available. A single score does not determine a universal winner.