AI Model Wiki

    Skip to main content

    Model Data Methodology

    Last updated: February 2026

    Every model page on AI Model Wiki shows structured data — pricing, context window, modalities, access type, sources. This page explains where each of those fields comes from and how we keep them honest.

    Field-by-field sources

    For each field below, our preferred source is listed first. We fall back to the next option only when the primary source isn't available.

    • Pricing — the developer's official pricing page; cited URL appears in the Sources block on each model page
    • Context window & max output — the developer's model documentation (model card, API reference)
    • Knowledge cutoff — published model cards or developer announcements
    • Modalities (input/output) — model documentation; tested in-house when ambiguous
    • Open-weight / license — the model's license file or Hugging Face card
    • API / web availability — direct verification (we sign up and confirm)
    • Benchmark scores — the benchmark's own leaderboard or the developer's self-reported figure with a citation; see Benchmark Methodology
    • Strengths / weaknesses / best use cases — editorial judgement informed by testing and citations; the editor's name is on file
    • Privacy & safety notes — developer's privacy policy, terms of service, and enterprise documentation

    The verification queue

    Proposed updates to structured fields land in an admin review queue, where an editor confirms each value against the cited source before it publishes. Approval stamps the model row with a fresh last-verified date and appends the citation to the model's Sources block.

    Every model has a colour-coded badge in the page header:

    • Verified — confirmed within the last 30 days
    • Last verified Xd ago — confirmed between 30 and 60 days ago
    • Needs update — older than 60 days
    • Needs verification — never editorially confirmed

    When data disagrees

    Sometimes the developer's own documentation contradicts itself (e.g., a context-window number in a blog post that doesn't match the API reference). When this happens:

    • API reference wins over a blog post
    • Newest dated source wins over older sources
    • If the disagreement is material (pricing, context window, model availability), we contact developer relations for clarification before publishing
    • If we can't resolve it, both numbers are shown with a note explaining the disagreement

    No invented data

    We do not invent pricing, context windows, benchmarks, release dates, or availability. If a field cannot be tied to an official source or a first-hand test, it is left null and the page is marked needs verification. Empty is more honest than wrong.

    Reporting outdated data

    Every model page has a Report outdated info link in the header. Reports route to the editorial team and feed into the verification queue. See Corrections Policy for response times.