Agents

The growth layer your AI agent can wire in.

AfterLaunch is an always-on growth engine for your SaaS. It tracks AI search, SEO, competitors and the communities where your customers decide, then drafts the moves that get you found. The agent surface opens that engine to software: an MCP server and a REST API your coding agent connects to, reads from and acts on.

Your agent already wires in hosting, a database and background jobs. AfterLaunch is the same kind of primitive for distribution: paste a few lines into the session that builds your product, and it can work on getting it discovered too.

What your agent can do

Read the Feed

The ranked backlog of growth moves AfterLaunch has prepared for your product: what to ship, why it matters, and the full draft body for each move. Your agent reads the product run, its automated loops and every drafted output from the same key.

Act on moves

Ship, skip, redraft or archive a move. The same actions as the buttons in the app, and a skip carries structured feedback that improves future drafts.

Run the engine on demand

Trigger a loop run, refresh an AI Visibility scan, or top up the Feed with fresh moves. These spend money, so each one is metered: charged once per logical event, replayed rather than rerun on a repeat, and capped per tenant per day and per month.

Set the dials

Adjust a loop’s autonomy rung. Social channels never accept full autonomy: publishing stays review-and-post by a human. Cadence control is part of the Founder plan.

Built agent-first

Everything is machine-readable by design: an OpenAPI document, an MCP discovery descriptor, and plain-language instructions for AI agents at /llms.txt. Keys are scoped (read, write, config), every metered action is idempotent, and per-tenant spend caps hold regardless of who, or what, is calling.

Get started

Two ways in, both copy-ready.

If you already have an AfterLaunch account

Mint an API key in Settings, then point your agent at the MCP endpoint. From Claude Code that is one command:

claude mcp add afterlaunch --transport http https://afterlaunch.io/api/mcp --header "Authorization: Bearer al_..."

If you do not have one yet

Paste this into Claude Code, or any MCP-capable agent, and it will set AfterLaunch up for you. It submits your site and email, you approve with one click from your inbox, and nothing runs until you do. Your free Growth Snapshot and trial start at approval.

Set AfterLaunch up for my product, then show me my growth moves.
Use my real site URL and email in step 1.

1. POST https://afterlaunch.io/api/v1/onboard/start with JSON:
   { "url": "https://my-product.com", "email": "[email protected]", "agent_label": "Claude Code" }
   No authentication is needed. Keep the device_code from the response.
2. Tell me to open the approval email and click it. Nothing runs until I do.
3. Poll POST https://afterlaunch.io/api/v1/onboard/poll with { "device_code": "<the code>" }
   at the interval the response returns. On approval it returns an API key,
   shown exactly once. Store it somewhere I can find it.
4. Connect over MCP:
   claude mcp add afterlaunch --transport http https://afterlaunch.io/api/mcp --header "Authorization: Bearer <the key>"
5. Call whoami to confirm the key. My Growth Snapshot and first moves
   generate in the background after approval, so the Feed starts empty:
   call list_feed, and if it has no moves yet, try again in 10 minutes.
   When moves arrive, summarise the top three for me.

Access is opening in waves. If a key or an onboarding request is refused, your wave has not opened yet.

Want the app before the wiring? Join the waitlist and AfterLaunch will reach out when your spot opens.