If you built a Custom GPT, a Poe bot, a Perplexity Page, or anything where you didn't ship code — we hear you. The four integration paths Boost Boss ships today are SDK-based and assume you control a server. You probably don't. We're building no-code monetization next, and we'd like you on the waitlist.
Join the waitlist →These are AI surfaces where the platform owns the runtime — you authored the prompt, the persona, the actions, the knowledge base. You don't deploy a server, and you can't ship an SDK.
You built a GPT in OpenAI's GPT Builder. It's listed in the GPT Store or shared privately. People chat with it. You'd like to earn from those conversations.
You built a Poe bot — yours or based on a server-side Poe app. Quora's platform handles the runtime. You handle the persona, the knowledge, the prompt design.
You write Perplexity Pages with curated AI-generated answers on a topic. You have an audience returning for the content. You'd like a revenue stream.
You shipped on Voiceflow, Botpress, Stack AI, FlowiseAI, or another no-code AI platform. You don't write JavaScript. The platform is your runtime.
Lumi SDK for MCP, Lumi SDK script tag, Lumi SDK for browser extensions, and Lumi API for Bots all expect a place where you can run logic — a server, a script, an extension manifest. Custom GPT authors and most no-code AI authors don't have that. The platform (OpenAI, Quora, Perplexity, Voiceflow, etc.) owns the runtime.
We could ship something half-baked here that wraps your prompts in a fragile workaround, but it would break the moment OpenAI updated their Custom GPT runtime, and your users would notice. So we're not doing that.
Instead we're collecting waitlist signal. If we hear from 30+ no-code authors with real audiences, we ship the integration. If we hear from 3, the path stays parked while we focus on the SDK doors that already work.
One email tells us what you built, where it lives, and roughly how many conversations or interactions it gets per month. If we ship a fit, you're first to know — and the first cohort gets an elevated founding-publisher payout for the first six months, same as our Founding Publishers.
Email info@boostboss.aiRight — that's the hard part, and the reason this is a waitlist. The most likely shape is a Custom Action that calls a Boost Boss endpoint, returns a sponsored block, and your GPT's instructions tell it to surface the block at the end of relevant answers. It's a constrained version of what the SDK does on a server. We're prototyping; we'll share what works once it does.
This is one of the things we're working out. Each platform has different content policies for what a Custom GPT or bot can serve. Some are clearly within current rules; some are gray. We won't ship a path that gets your GPT delisted, which is part of why we're going slow.
Honest answer: we don't know yet. The published per-impression CPM for our SDK doors trends $2-15 depending on audience and surface. No-code surfaces are likely to be at the lower end because of disclosure constraints. If your Custom GPT does 10K conversations a month and 1 in 5 surfaces a sponsored block, we're talking double-digit dollars per month at first, more as advertiser demand for AI surfaces matures. This is supplementary income, not a replacement for a job.
If your platform supports calling an HTTP endpoint and rendering returned content (text or markdown), we can probably integrate. Tell us in your email which platform — Voiceflow, Botpress, Stack AI, FlowiseAI, Dust, custom builds — and we'll add it to the prioritization list.
Welcome change of plans. One of our four shipping doors will fit — most likely AI Apps if you're going to deploy a web frontend, or Bots if you're moving to Discord/Telegram/Slack. Same publisher account either way; we move you over.
Yes — just say so in the email. We won't auto-enroll you; the waitlist is informational, not a contract.