Support
How to get help - email [email protected] with the X-Request-Id from the failing call.
NeuroAPI support is email-only, with one address for API, billing, and enterprise requests:
There is no live chat, phone line, or ticket portal today.
What to include in your email
Include:
- The
X-Request-Idheader from the failing response. (Every response carries one. It mirrors therequest_idfield on a sync response.) - The HTTP status code and the response body, if any.
- The approximate timestamp in UTC.
- Your account email and plan.
- A one-line description of what you expected versus what you got.
With the request_id, support can locate the exact call, the
rate-limit state, the mode, the cost_units charged, and the upstream
provider's status, all without the prompt or completion content.
What not to include
- Your full API key. Support already sees the prefix in logs and does not need the full secret. If you accidentally pasted one, revoke it from the dashboard and mint a new one.
- The full prompt or completion content unless the issue is
prompt-specific and you've cleared the content for sharing. The
request_idis enough for support. - Customer PII. Same reasoning -
request_idresolves the call without it.
Response targets
| Plan | Target |
|---|---|
| Starter | Best-effort |
| Pro | Standard |
| Enterprise | As contracted |
If you're on Enterprise and the issue is production-impacting, mention that explicitly in the subject so it's routed correctly.
Subject-line conventions
Prefix the subject so the message routes quickly:
| Prefix | When to use |
|---|---|
bug: | Something broke, here is request_id. |
billing: | Quota, invoices, plan changes, payment-method issues. |
enterprise: | Custom plans, dedicated support, contractual SLA. |
Vulnerability disclosure
Don't send security reports to this address. Email
[email protected] and follow the Vulnerability Disclosure
Policy. More
on the Security page.
Status & incidents
Live uptime and incident history are on the status
page. For incidents that affect a broad
surface, NeuroAPI also posts a note in the Changelog and
replies on open tickets. If you suspect an ongoing incident, send a
short email. You don't need a request_id, because support correlates
it internally.
Sales
Custom quotas, dedicated support, and contractual SLAs are negotiated
over email. Write to the same address with the subject
enterprise: ... and a sentence about your expected volume.