Talk to the team behind XVAPI.
Use one clear contact page for sales questions, technical support, billing issues, and partnership requests.
- 01
- Sales and procurement: within 1 business day
- 02
- Technical incidents: within 2-4 hours
- 03
- Security reports: immediate acknowledgment
TEAM CHANNELS
Choose the right contact path
Choose the closest contact path for your request so the right team can respond faster.
- 01
Sales
Business day reply
Pricing packages, enterprise plans, procurement, invoicing, and expected usage planning.
- 02
Technical support
Fastest support response
Model availability, request failures, billing issues, and usage diagnostics.
- 03
Partnerships
Business partnership response
Channel cooperation, distribution, integration partnerships, and ecosystem introductions.
- 04
Security
Priority triage
Responsible disclosure, credential exposure, abuse reports, and account integrity concerns.
WORKFLOW
What to send so we can actually help
The best contact pages reduce back-and-forth. Send enough context up front and the team can move directly to diagnosis, proposal, or execution.
- 01
State the request clearly
Tell us whether this is pricing, support, procurement, abuse, or partnership.
- 02
Attach operating context
Include the model, account, request time, billing impact, and expected behavior.
- 03
We assign the request
Sales, support, and security requests are handled by the right team.
- 04
Get actionable follow-up
Expect either a solution path, a clarification request, or a scoped proposal.
Before you contact us
Send context, not just emotion.
For technical issues, sending clean reproduction details is worth more than sending a vague complaint. For commercial requests, clear expected volume and region matter more than generic introductions.
- 01
Your account email or display name
- 02
Affected model and approximate request time
- 03
Whether balance, billing, or only latency is impacted
- 04
Expected volume, region, and procurement timeline for sales
Fastest contact
ops@xvapi.comIf you're unsure which contact to use, start with support and include the request details.
COMMON QUESTIONS
Most contact requests fall into these buckets
- Can you help choose models and pricing?
- Yes. We can review your model mix, expected demand, and launch plan before you go live.
- What should we send for billing disputes?
- Include request IDs, time range, affected model, and the wallet or order impact you observed.
- Do you support channel or reseller cooperation?
- Yes. Send a short summary of your audience, region, and expected partnership model.
- Where should security issues go?
- Send them to the security mailbox first. Include reproduction steps and impact scope, not just screenshots.
XVAPI
Keep communication on the same standard as the product.
A serious API business needs a serious contact surface. Reach the right team with the right context and get faster answers.