Contact
Questions, bug reports, or feature suggestions — we'd love to hear from you.
The fastest way to reach us is by email:
[email protected]What to include
- Bug reports: the tool name, what you input, and what went wrong
- Feature requests: what you'd like the tool to do
- API questions: your use case and the endpoint you're calling
- General: anything else — we read every message
Response time
We typically respond within 1–2 business days. For urgent API issues, mention "API" in the subject line.
Common questions
My API call is returning a 400 error.
The most common cause is a missing or incorrect field in the JSON body. Check the input schema in the API docs or in the /openapi.json spec. Include your request body and the tool slug in your email so we can reproduce it quickly.
Is there a rate limit?
There is a generous shared rate limit on the free tier — more than enough for personal projects, prototyping, and automated workflows with moderate traffic. If you need higher limits or a dedicated allocation, mention your use case in your email and we will figure out a solution.
Can I use these tools in a commercial project?
Yes. The tools are free to use — the API, the MCP server, and the web UI — for personal and commercial projects alike. See the Terms of Service for the full details.
I want to request a new tool.
Send a short description of what the tool should do — one input, one deterministic output — and we will consider it for the next release. Tools with a clear API use case (not just a UI feature) are prioritised.
Useful links
- API Documentation — endpoint reference for all tools
- /openapi.json — OpenAPI 3.1 spec
- About quickhelp.dev — what we build and why