Support
Use this page when you need help beyond the docs, including integration questions, account access, enterprise conversations, and service status.
Use this page when you need help beyond the docs, including integration questions, account access, enterprise conversations, and service status.
Contact paths
| Need | Best path | Include |
|---|---|---|
| Integration question | Product or developer support | Route family, request shape, expected behavior, and minimal reproduction |
| Account or model-access issue | Support with account context | Account email or organization, environment, model ID, and route |
| Enterprise deployment or security review | Sales or solutions team | Organization name, security requirements, SSO or BYOK needs, and timeline |
| Outage or degraded service | Status or support escalation | Time window, route, region if relevant, request ID if available, and observed error |
| Billing or invoice question | Support or finance contact | Account, plan, invoice period, and owner contact |
Before contacting support
Include the account, environment, route family, request ID if available, and a minimal reproduction when the issue is technical. Do not send API keys or other secrets in plaintext.
Technical issue checklist
For API issues, send enough context for support to reproduce the problem without receiving your secrets.
| Field | Example |
|---|---|
| Environment | local, staging, production |
| API family | OpenAI-compatible, Anthropic-compatible, Gemini-compatible, Media, AI Music |
| Route | /openai/v1/chat/completions, /gemini/v1beta/models/...:generateContent, or another public route |
| Model ID | The exact model value returned by Models API |
| Request ID | A gateway or application request ID, if your logs captured one |
| Timestamp | When the failure happened, including timezone |
| Error | HTTP status, error body, or stream/task status |
| Minimal reproduction | A sanitized cURL or JSON payload using ANYINT_API_KEY as a placeholder |
What not to send
Do not send real API keys, provider credentials, private customer data, full production prompts with sensitive content, uploaded private files, or screenshots that expose secrets. If support needs a request sample, redact secrets and replace customer data with a small synthetic example.
Faster self-checks
Before opening a support request, these checks often isolate the issue:
- Call Models API to confirm the model ID is available to the account.
- Verify the auth header for the route family you are calling.
- Retry with a minimal text-only request before testing images, files, streaming, or async tasks.
- Check Errors and Limits for status-code meaning.
- For task-based routes, confirm the task reached a terminal success or failure state before treating the output as ready.
Contacts
| Need | Contact |
|---|---|
| Product or technical support | [email protected] |
| Sales or enterprise conversations | [email protected] |