Bring your bots — bot platform in development.
A Discord-compatible bot API — REST plus a real-time gateway, slash commands, and webhooks. In development: when it launches, most existing discord.js bots will run by pointing them at Voidcom.
Discord-compatible by design
The bot platform is in development and not yet available — there's no developer portal yet, so you can't obtain a bot token today. It's designed so that the API will mirror Discord's REST routes and gateway opcodes, so the libraries you already know will work against Voidcom: with discord.js, you'll change the API host and gateway URL and log in with a Voidcom bot token — no rewrite.
- REST routes mounted under
/api/v10, shaped like Discord's - Bot-token auth with the
Authorization: Bot <token>header - discord.js connects by overriding the REST and gateway URLs
- discord.py works behind a small host-rewrite proxy or a fork that accepts a custom API URL
REST + real-time gateway
The API is designed to read and write messages, channels, servers, members, roles, and bans over REST, and to deliver events in real time over a WebSocket gateway that speaks Discord-style opcodes — HELLO, IDENTIFY, READY, HEARTBEAT, and DISPATCH.
- Message, channel, guild, member, role, and ban endpoints
- Reactions, pins, and typing
- Gateway with heartbeat and intent-gated event dispatch
Slash commands & webhooks
When it launches, you'll register global and per-server slash commands and respond to interactions, create webhooks for outbound messages, and pipe GitHub and Slack events straight into a channel with the built-in ingest adapters.
- Global and guild-scoped slash commands
- Interaction callbacks with Ed25519-verified delivery
- Webhook create / execute, plus GitHub and Slack ingest
Encryption-aware, independently deployed
The bot API is built as its own independently-deployed service, so it will scale independently from the core server. Once it's available, bots that send into encrypted channels will be able to fetch a user's public key to participate in Voidcom's hybrid post-quantum encryption.
- Standalone service with its own container and health probes
- Public-key endpoint for E2E-aware bots
- Voice is not yet exposed to bots — it's on the roadmap