Editorial Policy and Source Standards

Last updated: August 27, 2026

This policy explains how the OxAlpha.chat Editorial Team researches, verifies, updates, and corrects editorial content. OxAlpha.chat is an independent publication and is not affiliated with Z.ai, OpenRouter, or any other company discussed on the website.

Our editorial team

Articles use the shared byline OxAlpha.chat Editorial Team because research, source checking, editing, monitoring, and technical maintenance are collaborative. A team byline does not reduce our responsibility: factual claims must be traceable to evidence, uncertainty must be labelled, and material mistakes must be corrected visibly.

Source hierarchy

We prefer the strongest available evidence in this order:

Official developer announcements, model cards, documentation, repositories, licence files, and current pricing pages.
Current platform listings and structured platform data, including OpenRouter model and provider information.
Original benchmark papers, leaderboards, reproducible evaluation logs, and primary statements from the people who ran a test.
Reputable reporting or third-party research that identifies its sources and methodology.
Community reports, screenshots, fingerprinting work, and social posts, used only with clear attribution and appropriate caveats.

An inference is not presented as a confirmed fact. If reliable sources disagree, we explain the disagreement or qualify the claim instead of selecting the most dramatic version.

Fast-changing specifications, prices, and availability

Model IDs, provider routes, context limits, prices, quotas, licences, supported inputs, and free-access periods can change. Automated tracker data is scheduled to be checked twice a day. Provider outages, caches, rate limits, or failed checks may delay a visible update.

Where OpenRouter reports both model-level metadata and a current provider limit, we identify which figure is being described. A provider-specific limit is not presented as a permanent limit for every possible route. Readers should verify the live provider listing before making a purchase or production decision.

Benchmark standards

A benchmark number is useful only with context. Wherever practical, we identify the benchmark and version, exact model ID or route, date, number of tasks or runs, system prompt, reasoning or sampling settings, enabled tools, evaluation harness, scoring method, and whether the result is vendor-reported, independently reproduced, or community-reported.

Scores from different benchmark versions, routes, harnesses, prompts, or tool configurations are not assumed to be directly comparable. Small samples are labelled as small samples. Vendor results are not described as independent verification.

Comparisons and recommendations

We compare exact products, model versions, and access methods whenever possible. A monthly consumer subscription is not treated as equivalent to per-token API pricing. Conclusions focus on defined needs—such as self-hosting, a first-party workspace, a cloud ecosystem, multimodal tools, or search integration—rather than declaring one changing model family universally “best.”

Automation and editorial review

Automation may help monitor listings, calculate examples, flag changes, or organize research. Material factual claims and editorial conclusions are reviewed by the editorial team before publication. Automated output and AI-assisted drafts are not treated as sources and must be checked against the underlying evidence.

Corrections and updates

Accuracy matters more than defending an earlier version. To report an error, email [email protected] with the page URL, the statement in question, and a primary or otherwise reliable source.

Material factual correction: the page is corrected and receives a visible dated correction or update note where appropriate.
Product or price update: the page and reviewed date are updated when the change materially affects the guidance.
Minor edit: spelling, formatting, link repair, and clarity changes may be made without a separate notice when meaning is unchanged.
Historical reporting: an older article may be preserved with a dated note explaining what later became known.

Independence, advertising, and sponsorship

Editorial conclusions are not sold to developers, platforms, advertisers, or other third parties. Programmatic advertising, if enabled, does not give an advertiser advance review, approval rights, or control over coverage. Any sponsored or affiliate material introduced in the future will be labelled clearly at the point where it appears.

The browser chat at /chat/ is kept separate from advertising placements.

Core primary sources

Contact

For corrections, source material, benchmark evidence, or questions about this policy, contact [email protected].