Review desk Field records over first impressions

Published verdicts: 0

Canonical review recordsSelection is editorial

Only the models worth a buying decision.

We would rather publish five defensible reviews than five hundred scraped summaries. Inclusion should mean a model can lower the cost floor, raise the capability ceiling, or change whether an upgrade is worth paying for.

Read the publication bar
00

Desk status · September 2026

No firsthand verdicts. Four research profiles.

No model has a published AIModel.Reviews test verdict. The profiles below synthesize current documentation and attributed external evidence, with their limits visible.

Fieldwork
preparation

Externally researched profiles

Know the candidate before you run it.

Exact IDs, current API terms, integration constraints, and the evidence that still needs to be collected.

Review anatomy

Answer first. Receipts underneath.

Every published record will separate the thing tested, the setup used, what happened, and the conclusion a buyer can safely draw.

Anatomy previewNot a model verdict

MODEL / EXACT ID / DATE

Model name review

Current
Short verdict

One plain recommendation—who should use it, who should not, and the job where its premium starts to matter.

Best forThe work it clears comfortably
Skip it forJobs a cheaper option already handles
BreakpointThe first difficulty where reliability gives way
Human effortCorrection, verification, supervision, recovery
RoutineMulti-stepAmbiguousAutonomous
Working profileReliabilityKnown quirksAlternativesVerdict historyEvidence

Open test register

Three first ladders. No predetermined winner.

Status describes the protocol, not model performance.

R-001
Coding

Repository change ladder

From an isolated fix to an ambiguous, long-running repository job.

Protocol shaping
R-002
Research

Evidence-backed brief ladder

From bounded synthesis to conflicting sources and verification-heavy conclusions.

Bars in review
R-003
Documents & data

Extraction-to-analysis ladder

From schema-bound extraction to cross-document reasoning with silent-failure risk.

Planned

Living records

A review can become wrong while its URL stays the same.

Current

The tested identity and material buying conditions still match the record.

Retest required

A model, alias, price, tool, or harness changed enough to revisit the decision.

Stale

The record remains historical evidence but should not guide a current purchase.

Retired

The tested option is no longer available for the reviewed use.

Research is not a rating

Use a profile to choose the test—not the winner.

The repository-coding guide turns these four candidates into a bounded, evidence-conscious buying sequence.

Read the buyer guide