Contact
Talk to the peoplewho run xKiro.
Questions, partnerships or support — pick whichever channel suits you. A person on our team reads every message and replies.
xKiro team
We reply in Tiếng Việt and English
Telegram
Recommended@xkiro_support_team
Chat with our team in real time.
Facebook
fb.com/xKiro.offical
Follow updates and message us on our page.
Signed in? Questions about your account are fastest from the console — it already knows who you are. Open console support
Before you write
Most answers are one click away.
Our docs answer most questions faster than we can. When they don't, the channels above reach a person.
- Live status checkSee whether the API is answering from where you are, right now.xkiro.com/status
- TroubleshootingAn ordered checklist for a request that keeps failing.docs · troubleshooting
- Error codesWhat each status means, and whether retrying can help.docs · errors
- FAQThe questions people ask most often, answered.docs · faq
Writing to us
Get it solved in one reply.
Whether a problem takes one reply or ten depends almost entirely on the first message. Copy this template, fill it in, and send it on any channel.
Never send an API key
Not in a message, not in a screenshot, not in a request dump. If a key has leaked, revoke it in the console first — then write to us.
Found a security issue? Report it privately to [email protected] rather than in a public channel.
# What you expected to happen — one sentenceExpected: # What happened instead — one sentenceHappened: # The exact model ID, including the vendor prefixModel: # Date and time with timezone · once, or every requestWhen: # The full error body: type, code and messageError: # Does the same request fail with curl too?curl: # Any proxy or gateway between you and the APIProxy: