Send corrections and site questions to [email protected]. Do not send API keys, prompts, private invoices, account credentials, or other sensitive information.
How should you report a price correction?
A useful correction can be checked without guessing. Put the model and channel in the subject line, then include the exact current value shown on the site, the value you believe is correct, the affected pricing field, the date observed, and a direct provider-owned source URL.
Use the full displayed model name and identify whether the issue is official or OpenRouter.
Specify input, cached input, output, context, lifecycle, or fee information.
Link directly to the provider documentation or exact OpenRouter model page.
Include the observed date, region or tier, and a non-sensitive screenshot when needed.
What kinds of messages are useful?
- A standard token price changed on an official provider page.
- A model launched, entered preview, was renamed, deprecated, or retired.
- An OpenRouter mapping points to the wrong dated or provider-specific model.
- A context limit, caching rule, fee disclosure, source link, or calculation explanation is inaccurate.
- A page has an accessibility, mobile layout, broken-link, or crawlability problem.
Requests for paid ranking, hidden affiliate placement, or changing a price without a verifiable source are not accepted. Product announcements can be reviewed, but publication remains an editorial and data-quality decision.
What should you avoid sending?
Do not email API keys, passwords, authentication tokens, private prompts, proprietary datasets, customer information, billing exports, full invoices, or personal identity documents. The site does not need account access to verify a public list price.
If your evidence comes from a private contract or negotiated enterprise rate, describe the general pricing category without sending confidential terms. Private discounts do not normally replace the public standard rate in the catalog.
Can providers request attribution or removal?
Providers can report an incorrect source, trademark presentation, lifecycle state, or description through the same email address. LLM API Prices is an independent reference and does not imply endorsement or affiliation. Provider and model names remain the property of their respective owners.
Messages are reviewed for accuracy and site maintenance. A response time is not guaranteed, but clear corrections with direct sources are the easiest to verify. The methodology page explains how evidence is evaluated before publication.