Methodology
How we check what we publish
Every claim on theLLMs should be traceable to a source, a date, or an explicit caveat. This page explains the standards we apply.
Source checking
Before an article is published, the sources it relies on are checked against live URLs on the date recorded in the article's Scope field. This includes:
- Provider API documentation and pricing pages
- Published benchmark results and leaderboard data
- Regulatory guidance and standards documents
- Research papers and technical reports
If a source has moved, changed, or been superseded since the article was published, the Last checked date will be stale. Reader corrections are the primary trigger for rechecks between scheduled reviews.
Dates and freshness
Every article carries a Last checked date. This is the date the sources and claims in that article were most recently verified against live provider documentation or published data.
A Scope field on every article records the geographic, regulatory, and temporal boundaries of the piece — so a reader in a different jurisdiction or time period knows whether the guidance still applies.
Caveats and uncertainty
Articles are expected to flag uncertainty explicitly rather than projecting false confidence. Common caveat patterns include:
- Pricing that changes frequently and was correct on the stated date only
- Benchmark scores that depend on evaluation methodology and may not generalise
- Regulatory guidance that is operational, not legal advice
- Performance claims that depend on hardware, quantisation, or workload characteristics
Verification, not vibes
theLLMs does not publish claims based on "likely" or "probably" without evidence. If a source cannot be verified, the article either omits the claim or labels it as unverified with the reason.
When provider documentation is ambiguous, the article reports the ambiguity rather than resolving it with speculation.
Reader corrections
If you find a factual error, an outdated price, a broken link, or a claim that no longer matches its cited source, email the address on our Contact page. Corrections are logged, prioritised by reader impact, and applied with a visible date update on the article.
Last updated: May 2026