Set Up a Waitlist With Your AI Agent

You can set up a complete waitlist from inside an AI agent: give Claude, ChatGPT, Cursor, or OpenClaw your Waitlister account API key, point it at waitlister.me/skill.md, and ask for a waitlist. The agent creates the waitlist, builds and publishes the hosted landing page, and wires up signups. It works on every plan, and you never open the dashboard.

The landing page is usually the slowest part of a pre-launch. If you already work in an AI agent, skip the layout-fiddling: describe the page in plain language and let the agent do the setup.

What you need

Two things:

1. A Waitlister account. Free, no credit card.
2. An account API key (wl_acct_…) from Settings → API keys.

The account key works on every plan, including free, and it can create waitlists itself. Your agent can start from a completely empty account.

Set up the waitlist with one prompt

Paste something like this into your agent, with your key in an environment variable or config (not in a public repo):

"Set up a waitlist for my product BriefStack on Waitlister. Dark theme, developer aesthetic. Read waitlister.me/skill.md for the API. Publish the page and confirm it's live before you're done."

What happens behind that prompt:

1. The agent reads skill.md, which documents the whole flow for agents in one file.
2. One API call creates the waitlist and a draft landing page together: POST /api/v1/waitlists with a landing_page object (headline, description, button text, theme).
3. A second call publishes it. Your page is live at waitlister.me/p/your-slug.

Pages are drafts until they're published, so nothing goes live without an explicit publish step. Your agent can also take the page offline again with one call.

Per agent: Claude, Cursor, ChatGPT, OpenClaw

Claude and Claude Code. Point it at skill.md, or install the official MCP server so waitlist operations show up as native tools: @waitlister/mcp with your key in WAITLISTER_ACCOUNT_KEY. Fourteen tools, including create, publish, and stats.

Cursor and coding agents. The waitlister npm package covers the same surface in code:

import { Waitlister } from 'waitlister'
const wl = new Waitlister() // reads WAITLISTER_API_KEY

const { waitlist } = await wl.waitlists.create({
  name: 'BriefStack',
  landingPage: { headline: 'Join the beta', theme: 'dark' }
})
await wl.waitlist(waitlist.key).landingPage.publish()

If you're embedding the signup form in your own Next.js or React app instead of using the hosted page, follow the Next.js waitlist guide.

ChatGPT. Give it the key and the OpenAPI spec. The REST API is plain JSON over X-Api-Key auth, so any agent that can make HTTP calls can run the full flow.

OpenClaw. Install the Waitlister skill from ClawHub (openclaw skills search waitlister), set WAITLISTER_API_KEY, and prompt it. The skill carries the same instructions as skill.md.

Optional: have the AI design the page

The structured fields (headline, description, button text, background, theme) are enough for a clean page. If you want a designed one, your agent can call the same AI page builder that powers the dashboard: one API call with a design prompt, one AI credit per generation, and it takes under a minute. The design conversation carries over to the dashboard chat, so you can keep refining by hand later.

What your agent can and can't do

Your agent can create waitlists, build and edit pages, publish and unpublish, add signups, and read stats. On Growth and Business plans it can also manage subscribers.

Some things stay in the dashboard on purpose: custom domains, branding removal, tracking IDs, and image uploads can't be set through the API on any plan. An agent with your key can run your launch, but it can't quietly change the things you'd want to sign off on.

API keys are scoped to your account and revocable in Settings at any time. Signup email validation rejects fake addresses, so a confused agent can't fill your list with junk.

Verify it worked

Ask your agent to prove it, or check yourself in under a minute:

1. Open the page URL it reports. The page should render with your copy.
2. Sign up with a real email. You should get a queue position; on Launch and above you'll also get a referral link (the referral program is built in).
3. The signup shows in your dashboard, or via the stats endpoint.

FAQ

Does this work on the free plan?

Yes. Account API keys work on every plan, including free. Creating the waitlist, building and publishing the landing page, adding signups, and reading stats are all available; free-tier rate limits are lower. See pricing for what each plan adds.

Is it safe to give an AI agent my API key?

Keep the key in an environment variable, not in a prompt or a public repo, and revoke it in Settings if anything looks off. The API also limits the blast radius: plan-gated settings like domains and branding can't be changed through it at all, and pages never go live without an explicit publish call.

Can my agent edit the page after it's live?

Yes. Copy, theme, and SEO fields update through the API, and published pages update in place. Pages built with the AI designer keep their copy inside the generated design, so agents edit those through the design endpoint instead; the API tells the agent exactly that if it tries the wrong route.

Which agent works best?

Any agent that can make HTTP calls works. Claude and OpenClaw have first-class paths (MCP server, ClawHub skill), coding agents get the npm SDK, and everything else can use the REST API with the OpenAPI spec.

Helpful resources

• Quickstart — every path from zero to live, human version.
• API reference — all endpoints, auth, rate limits.
• Add a waitlist to a Next.js app — for embedding in your own site.
• Launching an AI product? — waitlist strategy for AI launches specifically.