Contact
Contact the team for technical support, account operations, and integration guidance.
1
Before opening a support request
Prepare reproducible technical details so support can diagnose and resolve issues quickly.
- Include workspace ID, endpoint, model, and request timestamp.
- Attach status codes, error payloads, and retry behavior.
- Share expected versus actual behavior with concrete examples.
- Mention whether this affects production traffic or testing only.
2
Incident escalation
Critical reliability and security incidents should be escalated immediately.
- Outages, severe latency spikes, and security concerns are top priority.
- Include impact scope: affected users, regions, and timelines.
- Keep a single incident thread to avoid fragmented context.
- Update support when impact changes significantly.
3
Integration and onboarding consultations
For new projects, we can help teams define a practical integration plan and rollout order.
- Choose initial models and fallback strategy per use case.
- Define key and workspace structure before production launch.
- Set budget alerts and reliability targets early.
- Establish prompt evaluation and regression review cadence.
4
Expected response windows
Response speed depends on issue severity and available technical context.
- Critical incidents receive immediate triage.
- Standard support requests are handled in queue order.
- Well-documented reports are resolved significantly faster.
- Policy and billing clarifications are provided in writing.