Contact us
Questions, bug reports and feature requests all go to the same inbox.
We read every message. If it is a bug report, include what you pasted and what you expected.
Contact
- Emailhello@example.com
- Phone+1-000-000-0000
- Office88 Example Avenue, Chaoyang District, Beijing
Send message
What happens to your message
Messages go to a shared inbox that all three of us read. There is no ticket queue and no automated triage, so a bug report with a reproducible input usually reaches the person who built that tool the same day.
We do not run your text through anything. If you paste a sample model reply into the form, we use it only to reproduce the problem, and it is not retained once the thread is closed. If you would rather not share the input, describe its shape instead — “a fenced JSON block followed by a summary sentence” is often enough to find the cause.
We reply in the language you wrote in, and we will not ask you to re-file the same request through another channel. If a fix ships, the thread gets an answer — you should never have to guess whether something was acted on.
Before you write
How do I report a bug?
Name the tool, paste the exact input you used, and say what you expected instead. Without the input we can usually only guess.
How long does a reply take?
One business day on weekdays. Bug reports that include a reproducible input usually get an answer the same day.
Do you answer usage questions?
Yes. "Which model should I route this prompt to" is a normal question, not a support burden.
Is there a support plan for the free tier?
No — the free tools are the product, and the same inbox serves everyone.
Can I request a tool that does not exist yet?
Yes, and it is the most useful kind of message we get. Describe the input, the output you want, and what you do today instead.
Something missing from the toolkit?
Tell us which tool you needed and what it should have done. The request list is short and we work through it in order.