For server admins
YATB is a private bot. If it is on your server, this is how you set it up. All commands are under /yatb and only visible to admins.
Setup in 5 steps
- Check permissions. In every linked channel YATB needs: View Channel, Read Message History, Manage Webhooks, Create Public Threads, Send Messages in Threads, Manage Threads.
- Link channels. Channels with the same bridge name are translated into each other:
/yatb bridge add chat #english English/yatb bridge add chat #deutsch German - Add API keys (optional). Without keys YATB uses LibreTranslate. For better quality add keys with
/yatb keys add- see API keys. - Set a log channel.
/yatb log set- YATB reports usage warnings, key problems and changes there. - Inform your members. Link to the member guide or add a short rule, for example:
Translation (YATB): In linked channels, the bot YATB translates messages automatically and reposts them under your name. For this they may be sent to external services (e.g. AI providers, Google). Message texts are not stored. Local-only translation: /yatb-user privacy
/yatb status shows the translation chain of your server and the state of every service.
The translation chain
For every message YATB tries the services in this order and takes the first good result:
- AI providers with your keys - better quality group first, free keys before paid keys
- Google Translate
- Azure Translator
- LibreTranslate on our own server - always available
- [Raw] - the original text, if nothing else worked
Every answer is checked (mentions, links, formatting). A bad answer, an error or an exhausted limit moves on to the next service; a failing service is skipped for a while. Members with Local only always get LibreTranslate.
Usage, limits and budget
- Free keys: YATB counts usage against the provider's free limits per minute, day and month.
- Paid keys: you set a monthly budget in USD or EUR. YATB estimates the cost from the list prices - set a spending limit at the provider as well.
- Daily limits reset at 00:00 UTC, monthly limits on the 1st at 00:00 UTC.
- Warnings at 90, 95 and 100 % go to the log channel. When a key is used up, the next service takes over.
- If the same key is used on several servers, usage is counted together. Other servers are never named.
/yatb keys listshows usage per key,/yatb keys editchanges plan, budget and limit.
How keys are protected
Keys are entered in a private Discord form, never as a command option. They are stored encrypted (AES-256-GCM, separate per server) and are never shown again - only the last 4 characters. This website never shows or accepts keys.
All commands
| Command | Description |
|---|---|
/yatb info | Setup guide and overview of all commands |
/yatb guide | How to get an API key for a translation service |
/yatb status | Translation chain, usage and service health of this server |
/yatb bridge add | Add a channel to a translation bridge |
/yatb bridge remove | Remove a channel from its bridge |
/yatb bridge list | List all bridges of this server |
/yatb keys add | Add an API key (entered in a private form, stored encrypted) |
/yatb keys edit | Change the settings of a key (the key itself is never shown) |
/yatb keys list | Show this server's API keys and their usage (never the keys themselves) |
/yatb keys remove | Remove an API key from this server |
/yatb log set | Set the channel for notifications (usage warnings, key problems, changes) |
/yatb log clear | Turn off the notification channel |
/yatb reset | Delete all bridges, keys and settings of this server |
/yatb uninstall | Delete all data of this server and make the bot leave |
/yatb-user privacy | Choose who may translate your messages (applies on all servers) |
/yatb-user help | What this bot does with your messages |
Removing YATB
/yatb reset deletes all bridges, keys and settings of your server. /yatb uninstall deletes all data of your server and the bot leaves.