Support
Get in touch
- General and billing
- support@guttertokens.com
- Report abuse
- abuse@guttertokens.com — misuse of the API, or content generated through it. See the Acceptable Use Policy.
- Security
- security@guttertokens.com — vulnerabilities and disclosure. Please report privately first and give us a chance to fix it.
Reporting a failed request
Our error responses do not include an internal request id. To let us find a specific call, include:
- When it happened, with a timezone — to the minute is enough.
- The first four characters of the API key used (shown next to each key in the dashboard). Never send the whole key.
- The model and the status code and
codeyou received. - Whether it was streaming.
Your own usage log in the dashboard lists every billed request with its timestamp, model and cost, which is usually the fastest way to identify the one you mean.
Before you write
- 401 — the key is wrong or revoked. Create a new one; keys are shown once and cannot be retrieved afterwards.
- 403 — out of credit. Check the balance on your dashboard.
- 503 — no capacity for that model. Check the name against the catalog and retry shortly.
- Balance looks low mid-request — an in-flight call reserves an estimate and refunds the difference when it completes. It settles within seconds.