For agents

Connect your agent

Five ways to authenticate, one set of tools. Every MCP tool has a JSON API twin under /api/v1.

1. Human first

Sign in, open Agents & API, create a credential with the scopes you want (optionally bound to one project) and paste it into your agent's secret configuration. Use it as Authorization: Bearer lb_agent_… against https://launchbase.build/api/v1 or as the bearer for the MCP endpoint.

2. Remote MCP with OAuth

Point an MCP client (Streamable HTTP) at https://launchbase.build/mcp. Unauthenticated calls return a 401 whose WWW-Authenticate header names /.well-known/oauth-protected-resource/mcp; the client registers dynamically at /register, runs the PKCE code flow through /authorize and /token, and you approve the requested scopes on the consent page. Tokens are short-lived with rotating refresh tokens; revoke any grant under Connections.

3. Agent first

An agent without an account calls POST /api/v1/agent/drafts with a description (and your email), receives a draft session token and a claim link. It can refine the draft over MCP (draft_status, draft_update). You sign up or sign in and claim the draft as a project; the agent then calls draft_redeem once to receive a credential bound to that project. Nothing is provisioned or charged until you subscribe.

4. Connect link

The agent calls POST /api/v1/agent/connect with its name and receives a short code and a link (https://launchbase.build/connect/ABCD-EFGH). You open it, sign in with whatever you use, tick the scopes you want to grant, optionally limit it to one project, and approve. The agent polls GET /api/v1/agent/connect/{id} with its poll token and receives its credential once. Nothing to copy.

5. Preauthorized machine

Under Connections an owner issues a one-time invite code with scopes, an optional project binding and a spend limit. The agent redeems it with POST /api/v1/agent/redeem and receives its own credential; no further confirmation is needed within that policy.

Entry points

GET https://launchbase.build/api/v1/discovery      # endpoints and status
GET https://launchbase.build/api/v1/guide          # stacks, port/health contract, limits, upload → release → logs
GET https://launchbase.build/api/v1/catalog        # components, regions, plan, features
GET https://launchbase.build/llms.txt

// Streamable HTTP, stateless
{ "mcpServers": { "launchbase": { "url": "https://launchbase.build/mcp",
    "headers": { "Authorization": "Bearer lb_agent_…" } } } }
// or leave headers out and complete the OAuth flow the server advertises

curl -X POST https://launchbase.build/api/v1/agent/connect \
  -H "Content-Type: application/json" -d '{"agentName":"Claude Code","description":"Deploy the notes app"}'
# → { "userCode": "ABCD-EFGH", "verificationUrl": "https://launchbase.build/connect/ABCD-EFGH", "pollToken": "lb_connect_…" }
curl https://launchbase.build/api/v1/agent/connect/<connectId> -H "Authorization: Bearer lb_connect_…"
# → { "status": "pending" } … { "status": "approved", "token": "lb_agent_…", "mcpConfig": { … } }

curl -X POST https://launchbase.build/api/v1/agent/drafts \
  -H "Content-Type: application/json" \
  -d '{"description":"Notes app with teams and a monthly subscription","ownerEmail":"you@example.com"}'
# → { "draftToken": "lb_draft_…", "claimUrl": "https://launchbase.build/claim/…", "mcp": "https://launchbase.build/mcp" }

Contract

Provider master credentials are never issued to agents. Payments, domain purchases and provider onboarding always return an action_required URL for the owner. Every action is audited with its actor, and cross-account ids answer 404.