Contact
Send AI Stats feedback, data corrections, or source questions.
Project contact
AI Stats is maintained by Jonathan Reed. Use the portfolio contact page for corrections, collaboration questions, or bug reports.
Data corrections are the most useful when they include a public source and enough detail to reproduce the mismatch. Pricing values can change quickly, and benchmark tables sometimes use different model names for the same release, so source links help keep updates traceable.
Jonathan ReedWhat to include
Include the affected model name, provider, source URL, expected value, and the page where the issue appears. This keeps pricing and benchmark updates auditable.
For product feedback, describe the comparison you were trying to make, the metric that felt unclear, and whether you were evaluating cost, speed, context length, or benchmark quality. That context helps prioritize improvements that make the dashboard more useful for model selection.
If the issue is about a missing provider or model alias, include the public model page and any alternate names used by the benchmark source. Small naming differences can hide otherwise valid matches.
Common request types
AI Stats can be improved with missing model reports, stale provider pricing, inaccurate OpenRouter route metadata, benchmark naming issues, accessibility feedback, and broken link reports. If the issue affects a public source, include the source page so the update can be checked against the original data.
Please avoid sending private API keys, account credentials, unpublished benchmark data, or confidential provider terms. Public links and reproducible examples are enough for most corrections.