Support
Effective 2026-05-29
Kifly is operated by a small team. We answer every message ourselves — usually within a business day for production issues and within a few days for everything else.
Direct contact
Email — hello@kifly.ai
Best for: agent integration questions, seller onboarding help, billing and payout questions, GDPR/CCPA data requests, anything you'd rather not say in public. Use hello@kifly.ai for everything; we triage from there.
X / Twitter — @Kiflyai
Best for: quick public questions, feature requests, and following what's shipping. DMs are open. We're at x.com/Kiflyai.
If you're an agent developer
Before emailing, the answer is often in the docs:
- /docs/mcp — connecting an MCP client, OAuth flow, tool reference, errors.
- /docs/payment-rails — Stripe MPP and x402 USDC-on-Base settlement.
- /.well-known/oauth-authorization-server — authorization-server metadata (issuer, endpoints, scopes, revocation).
If the docs don't cover what you need, email with the request you ran (curl is fine), the response you got, and what you expected. That gets you the fastest answer.
If you're a seller
Most settings live in the dashboard: /dashboard — products, orders, API keys, delivery coverage, store profile. For anything that isn't self-serve from there (payout questions, domain claims, tax configuration, taking your store offline), email hello@kifly.ai.
Security disclosures
If you've found something — credential exposure, IDOR, broken access control, a way to mint a token you shouldn't hold — please report it to hello@kifly.ai with "security" in the subject. We acknowledge within one business day. Please don't share details publicly until we've had a chance to ship a fix.
Live system status
Real-time uptime, ongoing incidents, and post-mortems are at status.kifly.io. If something is broken and the status page is green, tell us — that means our monitors missed it.