For AI Bot Developers

Turn your AI bot into a revenue-generating business.

Lumi API for Bots — one REST call from your bot's response handler. Works with Discord, Telegram, Slack, and any platform your bot lives on. Any LLM. Any framework. Optional per-platform helper libraries available.

Start as a publisher →

See it appear

Your bot replies first.
The sponsored message arrives right after.

Same campaign renders natively on Discord, Telegram, and Slack — embed, card, or attachment, depending on the platform. Helper libs handle the formatting.

A Telegram bot reply followed by a sponsored card

Phone-shaped Telegram preview shown here. The same Lumi API for Bots response can be formatted as a Discord embed, Slack attachment, or Telegram card — see the static preview below for all three side-by-side.

How it works

From API key to first ad in ten minutes.

Get your API key

Call Boost Boss

Hit POST /v1/ad-request from inside your bot's response handler with the user's query as context.

Format and send

Use our helper libs (lumi-discord, lumi-telegram, lumi-slack) to convert the response to native message format.

Integration snippet

A few lines, your existing handler.

// Inside your Discord bot's response handler — Lumi API for Bots:
const { ad } = await fetch('https://boostboss.ai/v1/ad-request', {
  method: 'POST',
  headers: {
    'Authorization': `Bearer ${API_KEY}`,
    'Content-Type':  'application/json',
  },
  body: JSON.stringify({ format: 'embed', context: userQuery, platform: 'discord' })
}).then(r => r.json());

message.reply({
  content: aiResponse,
  embeds: [toDiscordEmbed(ad)]   // from optional @boostbossai/lumi-discord
});

Optional helper libraries (lumi-discord, lumi-telegram, lumi-slack) are convenience wrappers around the Lumi API for Bots — they format the ad payload into each platform's native message type. Skip them and roll your own formatting if you'd rather not add a dependency. Full docs →

Sponsored block on Discord, Telegram, and Slack

Same campaign, three native message formats. The helper libs (lumi-discord, lumi-telegram, lumi-slack) handle the platform-specific formatting.

Who this is for

If your bot lives in a chat platform, this is your path.

✓You shipped an AI bot on Discord, Telegram, or Slack.
✓Examples: research bots, summarization bots, image generation bots, productivity assistants, customer support bots.
✓You want monetization that doesn't require a paywall — your community uses it free, you earn from ads.
✓You're tired of "tip me on Buy Me a Coffee" being your only option.

Revenue example

What 15,000 daily users can earn.

Illustrative — not a guarantee

Daily active users15,000

Ad impressions per user per day~1.5

Daily impressions22,500

CPM (varies by platform)$2

Monthly publisher revenue~$1,350

Numbers are illustrative for a moderately-active community bot. CPMs vary widely by platform — Slack workplace audiences pay more, Telegram consumer audiences less. Vertical and language also matter; English-language productivity bots sit at the top of the range.

Frequently asked

The questions every bot dev asks.

Will this violate Discord / Telegram / Slack ToS?

Lumi is designed for ToS compliance. Discord requires clear ad disclosure; we handle that with a "Sponsored" prefix and the disclosure label you configured in your dashboard. Telegram and Slack have looser policies but we follow best practices regardless.

Can I serve image ads, not just text?

Yes. Discord embeds support image fields; Telegram supports inline media; Slack blocks support image accessory components. The helper libraries map a single ad payload to whichever format your platform uses.

What about non-English bots?

Boost Boss serves ads in 40+ languages. CPMs vary by market — large EN, ES, JA markets pay best; smaller-language inventory still fills but at lower rates.

Do I need to handle click tracking myself?

No. Use the click_url we return in every ad response — tracking is built into that redirect. Same for impression tracking via impression_url.

What's the rate limit?

1,000 ad requests per minute per publisher on launch. We raise that for verified-volume publishers; tell us if you're approaching the cap.