Please don’t send API keys, passwords or other secrets by email. Nobody needs them to look into a problem.
What to include
Reporting a wrong price or model limit
Include the model name, the page you saw it on, and a link to the provider’s pricing page or docs that shows the correct value. Prices are refreshed automatically every day, but providers sometimes change prices before the public data sources catch up.
Reporting a broken tool
Tell me which tool, what you did, what you expected and what happened instead. Your browser and device help too. If the problem involves text you pasted, a short example that shows it is enough; don’t send anything confidential.
An error fix that didn’t work
Include the exact error message, the tool and version you’re using (for example, the output of claude --version), your operating system, and which steps you tried.
Suggesting a tool
Describe the job you’re trying to do and how you do it today. The most useful suggestions are about small, repetitive tasks that are annoying to do by hand.
Corrections
When something is wrong, I fix it and update the page’s “last updated” date. Significant corrections are noted on the page itself. See the methodology for how data is collected and checked.
Privacy
Emails are used only to reply to you and improve the toolkit. They’re never shared or added to a mailing list. See the privacy policy for details.