Feedback
If you run into issues while using MoleAPI, or have requests for new features, feel free to send feedback. This page focuses more on a "user perspective" feedback workflow, rather than asking you to file an issue on GitHub.
🧾 Please prepare this information before submitting feedback
The more complete your information is, the faster we can identify the issue
At a minimum, prepare screenshots or the full error message. If you can also include the model name, Base URL, client you used, and reproduction steps, troubleshooting will be much more efficient.
It is recommended that you organize the following information first:
- Error screenshots, or the complete error text that can be copied
- The model name, application name, and Base URL you used
- The approximate time when the issue occurred, and what actions you performed
- If the issue is related to billing, cache hits, or balance, it is best to include a screenshot of the usage details
📮 Recommended ways to submit feedback
You can handle it in the following order:
- First check FAQ and Common Error Codes
- If the issue is still not resolved, go to the QQ groups listed on the Community Interaction page and submit feedback there
- When submitting feedback, send all key information at once instead of only saying "it doesn't work" or "there's an error"
🐞 What kinds of issues are appropriate to report?
- Usage issues, such as common errors like 400 / 401 / 403 / 404 / 429 / 500
- Balance, Quota, cache retrieval, or billing results that are unclear
- Whether a specific model is available, or why its behavior differs from expectations
- Unclear documentation, misleading page descriptions, or outdated screenshots
- New features or new capabilities you would like to see added
💡 How can you make feature suggestions more effective?
If you need a specific feature, you can also submit a suggestion directly. Compared with simply saying "I want this feature," the following format is much more likely to be accepted:
- What feature you want
- How you plan to use it
- What is currently blocking you
- What cost this feature would save for you, or what problem it would solve
The most common issue when submitting feedback
Sending only "it doesn't work" or "there's an error" usually makes it very difficult to identify the issue. If you come with at least two or three of the following—screenshots, error text, model name, and operation steps—the process will be much faster.
How is this guide?
Last updated on