Discord bot template

Join the LivePair Discord — prompts, showcases, and support: discord.gg/3JrCAmv8A

livepairai/livepair-bots is a self-hostable Discord bot — clone it, drop in your lp_ key, and your server gets /imagine and /video slash commands backed by the live model catalog. Every generation bills your key, and every result carries a via livepairai.com footer that advertises the API to whoever watches the channel.

Deploy

One-click on Render (free plan): the repo ships render.yaml — hit the Deploy to Render button in the README, fill PUBLIC_KEY, APP_ID, LP_KEY, and point the app's Interactions Endpoint URL at the deployed /interactions path.

Or by hand:

git clone https://github.com/livepairai/livepair-bots
cd livepair-bots && cp .env.example .env   # fill APP_ID, BOT_TOKEN, LP_KEY
node register-commands.mjs                 # registers /imagine + /video
node discord-bot.mjs                       # start (npm run discord)

APP_ID / BOT_TOKEN come from the Discord Developer Portal — enable Public Bot and the bot + applications.commands scopes.
LP_KEY is an lp_ API key from Settings → API keys.

Commands

Command	What it does
`/imagine prompt:… [model:id]`	Image generation — `model` validated against the live catalog
`/video prompt:… [model:id]`	Video generation — polls async jobs, posts the result URL

Models marked private (-private ids) only respond in the bot's DMs or channels flagged NSFW — Discord's own channel flag is the gate, so public server channels can't trigger them.

All successful generations bill the operator's lp_ key — quotas and per-user limits are the operator's choice to add.

Posting results to X/Twitter

Two ways, both in the same repo:

twitter-bot.mjs — zero-dependency CLI: generate → upload to X → post. Your own X app keys in env vars; OAuth1.0a signing is built in. Runs from cron/CI.
n8n-x-workflow.json — the same pipeline as a visual workflow (community node @livepairai/n8n-nodes-livepair + X OAuth2 credentials) — see n8n node.

The X free tier can post tweets and upload media; it just can't read timelines — fine for a poster bot.