Send a precise correction, removal request or question about the reference. Include the affected page and useful evidence while removing credentials and private application material from your message.
Contact [email protected]. Use a descriptive subject that identifies the provider and the purpose of the message.
Report a data correction
- Affected page URL and exact model or field.
- What the page shows and what the official source establishes.
- Direct official source URL and when you observed the discrepancy.
- Any relevant condition such as processing mode or account scope, without personal identifiers.
Report an example problem
Include the endpoint, exact model identifier, installed SDK version and a minimal redacted reproduction. Distinguish an actual provider response from a schematic example or an inference about the problem. Do not send an entire repository or production conversation when a small safe fixture can explain it.
Remove these details before sending
- API keys, passwords, access tokens and session cookies.
- Personal data, confidential documents and unrelated customer records.
- Unnecessary account identifiers and private deployment information.
- Source code that is unrelated to the smallest reproducible problem.
Corrections and removal requests
Read the editorial policy for the review process and the disclaimer for independence and removal information. Takedown requests receive prompt action; a precise URL helps identify the material quickly.
Use the AI API cost calculator to turn the model and workload you are considering into an estimate.
Last verified · Source ↗
Frequently asked questions
Where should I send a correction?
Do I need to send my API key?
What is the best source for a price correction?
Should I attach my full application?
Can I request removal of material?
Sources
Last verified · Source ↗