Livepeer Agent · Discord Bot Setup

Set up the onboarding bot — Discord side

You own the Discord server. This is the ~8 minutes of Discord-portal clicks that only you can do (they're tied to your Discord account). When you finish, you hand four values to the engineer — they wire up the rest. One task comes back to you at the very end.

Time ~8 minYou need admin of a Discord server + the developer portal

You do (this guide)

  • Create the Discord app + bot
  • Copy 3 values + your server ID
  • Invite the bot to your server
  • Hand the four values off
  • Later: paste one endpoint URL

The engineer does (not you)

  • Puts your values in the hosting config
  • Deploys the bot's endpoint
  • Registers the /announce command
  • Flips the feature on

Steps

  1. Create the Discord application

    Go to discord.com/developers/applications → New Application. Name it Livepeer Agent Onboarding. Open the Bot tab → Add Bot. No privileged intents are needed — the bot uses slash commands, not the gateway.

  2. Copy three values

    Collect these — you'll send them to the engineer in step 4:

    ValueWhere in the portal
    Application IDGeneral Information → Application ID
    Public KeyGeneral Information → Public Key
    Bot Token secretBot → Reset Token → copy (shown once)
    The Bot Token is a password. Send it to the engineer over a secure channel (a password manager or DM) — never paste it into a public channel or a shared doc. If it ever leaks, hit Reset Token and send the new one.

  3. Get your server (guild) ID

    Turn on Developer Mode: User Settings → Advanced → Developer Mode ON. Then right-click your server icon → Copy Server ID. That's the fourth value — it lets the engineer register the command to your server so it appears instantly.

  4. Invite the bot to your server

    Portal → OAuth2 → URL Generator. Tick scopes bot and applications.commands. Under Bot Permissions tick: Send Messages, Create Public Threads, Send Messages in Threads, Embed Links. Open the generated URL, choose your server, Authorize.

  5. Hand off the four values

    Send the engineer the four values you collected. That's your part done until they come back to you:

    Application ID  : ...
Public Key      : ...
Bot Token       : ...   (send securely)
Server (guild) ID : ...

  6. Paste the endpoint URL after the engineer deploys

    The engineer will tell you when the bot endpoint is live and give you a URL. Then go to portal → General Information → Interactions Endpoint URL, paste it, and click Save:

    https://agent.livepeer.org/api/discord

    Discord sends a signed test to that URL; the field turns green only if it verifies. If it errors, tell the engineer — it usually means the deploy or the Public Key isn't in place yet. Don't paste this before they say it's ready.

What "done" looks like

A provider you've never met types /announce in your server, fills in a short form with their discovery URL, and their healthy capabilities are registered on the Livepeer Agent within seconds — no meetings, no tickets. That's the loop this setup turns on.
Decide who can run /announce. Anyone who can use slash commands in your server can run it. Keep it to a dedicated onboarding channel and restrict that channel's access if you want a gate — in Server Settings → Integrations → your bot, you can limit which channels the commands appear in.

If something's off

SymptomCause / fix
Endpoint URL won't turn greenThe engineer hasn't deployed yet, or the Public Key doesn't match. Confirm with them, then re-save.
/announce doesn't show upCommands not registered yet (engineer's step), or the bot isn't in the server (step 4). Server-scoped commands appear instantly; global ones take up to ~1h.
Bot can't reply / make a threadMissing permissions — re-run the invite in step 4 with all four permissions ticked.
This is the Discord-side setup only. The hosting config, deploy, command registration, and the onboarding pipeline are the engineer's side — see the go-live checklist. You do this once.