Find the source of a problem
Separate account, key, request-format, and upstream errors. Use the request ID to connect the evidence.
Start with error details in usage logs. Status codes below are starting points; use the specific message and request log to determine the cause.
Accounts and verification
Do I need a separate MomBench account?
No. MomBench uses the main site’s unified account, with separately assigned business roles.
Why did email verification fail?
Check your email address, spam folder, and browser security check. Retry as directed. If it persists, contact support with the time and error message. If you cannot sign in, email [email protected].
Common API errors
| Symptom | Check first |
|---|---|
| 401 / Authentication failed | Valid, enabled key and the Bearer authorization header |
| 403 / Access denied | Group permissions, model restrictions, security checks, and the specific denial reason |
| 404 / Route not found | API domain, duplicated /v1, and endpoint format |
| 400 / Invalid parameter or model | Full model ID, endpoint, streaming requirements, and the parameter named in the error |
| 429 / Request limited | Rate, concurrency, quota, and upstream reason; retry after the stated delay |
| 5xx / Gateway or upstream failure | Retain the time and request ID; avoid unlimited immediate retries |
“Model price is not configured”
This indicates incomplete billing configuration on the service, usually not an API key format problem. Contact support with the full model ID and request ID, and retry after configuration is confirmed. Renaming a model is not a valid way to bypass billing checks.
A visible model may also fail because of group permissions, channel availability, or the wrong endpoint. Use the full error message to distinguish these cases.
Why did a request fail after producing text?
A stream can produce partial text before an upstream error, timeout, or disconnect. Retain the ending event and any trailing error. The first token or HTTP 200 alone is insufficient to confirm success.
For channels requiring streaming Responses, use /v1/responses with stream: true, and a client that supports that format.
Top-ups, invoices, and refunds
Check currently available features in the wallet. Payment, invoice, and refund arrangements depend on actual service rules and support confirmation; contact support if you need to confirm an arrangement.
Help support reproduce the issue
- Time of the issue and your time zone.
- Client name, version, and full model ID.
- Endpoint, HTTP status, complete error message, and request ID.
- Whether streaming was enabled, reproducibility, and steps already tried.
Remove API keys, passwords, verification codes, cookies, and private prompts from screenshots and logs. Open a support ticket →
Include a request ID and error message in your ticket. Never include your API key.