Corrections Policy
Last updated: 2026-09-27
Our accuracy commitment
China AI Hub publishes factual data about China's AI ecosystem — model specifications,
pricing, benchmarks, releases and relationships. Every record is sourced and date-stamped
with a last_verified date. Analysis is labeled separately from observed data.
How to report an error
If you believe a fact, price, benchmark score or relationship on this site is wrong or outdated, email us with:
- The page URL (main site or Data Hub)
- The specific claim or value that is wrong
- The correct value and a link to an official source (vendor documentation, model card, official pricing page)
Contact: Martin.W — [email protected]
Alternatively, open an issue on the public project repository (github.com/martinxionbiotech-max/china-ai-hub/issues), using the same three details above. Both channels reach the same team.
What happens next
- We verify the claim against the official source you provide (or our own re-check).
- If confirmed, we update the record, refresh its
last_verifieddate, and note the change where relevant (e.g. price history entries). - If we cannot verify, we mark the value "Not publicly documented" or remove it rather than guess.
Correction timeline
We aim to act on verified corrections within a few working days. Data on Chinese AI pricing and releases changes quickly; we run periodic re-verification cycles across all records in addition to ad-hoc corrections.
Correction record
Material corrections — changes to a published fact, price, benchmark score, or relationship — are listed here in reverse chronological order, so the record is visible rather than buried in a commit log.
No corrections issued to date. As of 2026-09-29, no published fact on sinoaihub.com has required a public correction. When the first correction occurs, it will be recorded in this section with the date, the affected page, the before/after value, and the source that justified the change.
Ongoing data changes (price updates, new model versions, deprecations) are routine updates
rather than corrections, and are tracked in the project changelog documents
(docs/phase2-changelog.md and later phase changelogs) and in per-provider
price_history entries on pricing pages.