Build bots for Multiverse
Create an application, mint a bot token, and connect to the gateway — all self-serve, from any claimed account. No waitlist, no approval queue.
Open Multiverse and head to Settings → Applications — any claimed account can create one.
What exists today
Self-serve applications
Create an OAuth2 application from Settings → Applications. Give it a name, description, icon, and tags — application identity lives on the application, not its bot's avatar.
Named bot tokens
Mint multiple named tokens per bot, like prod-eu or ci. Each secret is shown exactly once and can be revoked individually, so you can rotate credentials without downtime.
Developer teams
Collaborate through invite-based teams with admin, developer, and read-only roles. Nobody is added to a team without accepting, and every application keeps a human owner.
In-app developer portal
Manage applications, tokens, and teams from Settings inside Multiverse — there's no separate portal to sign into.
A typed SDK
@fluxer/bot_sdk is a thin TypeScript client for REST and the gateway, with reconnect, resume, rate-limit handling, and typed errors built in. It's young — expect rough edges and fast iteration.
Familiar semantics
The gateway speaks HELLO, HEARTBEAT, IDENTIFY, and RESUME; REST uses the Bot authorization scheme and snowflake IDs. If you've built for Discord, you'll feel at home.
What's not built yet
We'd rather tell you now than have you find out mid-project.
Interactions
No slash commands, buttons, or modals yet. Today, bots read and send messages.
Sharding
The gateway tells you how many shards to use, and the answer is currently always one. Read it, don't assume it.
Intents
There's no intents bitfield. A named event-subscriptions model is planned instead.
Bot directory
No public bot listing yet — you invite your bot to servers with an OAuth2 link.