Bots

Who this is for: people who chat with bots, room admins who install workers, and anyone checking whether bots are end-to-end encrypted.

Developer API: Bot API · Worker bots · Console: developers.buzzio.dev

What it is

Buzzio lets third-party developers run bots. Buzzio delivers messages and enforces limits; the developer’s server writes what the bot says.

Two kinds — chosen once in Forge, never converted:

You  →  Buzzio (delivery + short retention)  →  developer webhook
 ↑                                              |
 └──────────── bot reply (sendMessage) ─────────┘

Hard exclusions: no bots in sealed person-to-person chat, Whisper private chat, Whisper Questions, or E2E groups.

How to use (users)

Chat with a service bot

1. Search the bot’s @username (handles end in bot). Draft / rejected / paused bots do not appear.
2. Open the profile. You should see a Bot badge (Forge shows Official).
3. Tap Start (Buzzio’s button — same word on every bot). Accept Bot Terms if prompted.
4. Buzzio sends a platform /start event to the developer. Their welcome text is whatever their code replies.
5. Send more text. Each message is delivered to their server so they can answer.
6. Optional: Report or hide the bot — Safety.

Media a bot sends is usually an HTTPS URL the developer hosts. Your phone loads the file from them; Buzzio stores the link, not those outbound bytes. A file you send to a bot may be stored by Buzzio (currently up to 2 MB) for about 7 days so the bot can fetch it.

Install a worker (admins)

1. Open an open-history group or Community → Bots.
2. Look up @mod_bot (workers are not in people search).
3. Pick OHG permission ticks or Community roles → send a request.
4. The developer Accepts on developers.buzzio.dev (Requests). Pending ≠ installed.
5. After accept, the room shows a privacy label that a worker can read allowed messages.

Platform slash (admins only; never forwarded to the worker):

/bots
/bots list
/bots add username
/bots remove username
/bots perm username <grant> on|off

Members who type /bots get an admin-only message; that text is not sent to the room as a normal post.

Privacy strip

Banner expectation (every bot / Forge chat):

This chat is not end-to-end encrypted. The bot developer’s server can receive what you type.

Do not send recovery phrases, passwords, payment secrets, or anything you would not give that developer.

Legal: Bot Terms · Bot Privacy · hub: Legal and policies

What happens to your data

Clearing the chat removes the local copy. Reinstalling only restores text still within Buzzio’s retention window.

Forge (developers on the phone)

Forge is Buzzio’s official manager bot. Its brain runs on Buzzio — not a third-party webhook.

1. Search @forge_bot and open Forge chat.
2. Read the official / not-E2E banner.
3. Use guided commands:

Create on the phone (owner = Buzzio ID). Connect code on the desktop site with the token. Seed never goes to developers.buzzio.dev.

Bot lifecycle (what users / owners see)

Username rules (product): ends in bot; unique across people and bots; reserved prefixes such as buzzio_, forge_, support_ are blocked.

Safety

• Report works on bot chats the same job as 1:1 — Safety.
• Buzzio may pause, suspend, or delete a bot, or act on the owner’s Buzzio ID (all their bots).
• Developers must not use bots for scams, CSAM, phishing, or other Bot Terms violations.

Limits and honest ceilings

• Users can send text and supported files (currently up to 2 MB); bots may reply with text or developer-hosted media URLs.
• Bot premium is not offered. Membership-flag, checkout, and paid-access API names return 404.
• Workers only act after Console Accept and only with granted permissions. Workers cannot get Community administrator / manage_roles.
• If the developer’s server is down, the bot is down. Forge stays up.
• Full HTTP surface: Bot API · room tools: Worker bots.

Troubleshooting

Troubleshooting · FAQ

Related

• Sealed vs shared
• Groups · Communities
• Developer integrations
• No public messaging API