Product access
Ask about Scrawl, Communications, or DevOps: fit for your use case, what exists today, and how access works before public launch.
Email about thisContact
Bring us the operating problem.
Email is the direct line to ApexAi. Choose the path that fits and your email application opens with a subject line already filled in. Custom development has its own structured request.
Contact paths
Start with context.
Useful details: the product, who would be calling it (people, software, or agents), the workflow you want to run, the providers or proxies you already use, and what a good outcome looks like.
Technical integration
Discuss connecting software through ApexAPI, agents through ApexMCP, or your own providers and proxies to a product.
Email about thisSupport and general
Questions about the website, the products, or anything that does not fit another path.
Email about thisCustom work
Bots, integrations, automation, and tooling outside the packaged products. Submit a project for review; each request is scoped individually.
Request a custom buildSuggestions
An idea for a product, a gap you keep hitting, or feedback on this site. Short is fine, and no reply address is needed.
Send a suggestionDirect
Sales and support.
Contact is by email; no account is needed. Sales and Support are separate inboxes, so each message reaches the one that acts on it.
- Sales: product access, technical integration, and Custom Orders
- sales@apexaiofficial.com
- Support: help, general questions, and Suggestions
- support@apexaiofficial.com
- Launch news and product updates
- ApexAi Official on Telegram
- Public questions and discussion
- ApexAi Central on Telegram
Keep account details and private business information out of public chats; email is the place for those. No conversation with ApexAi needs a password, key, or token to get started.