For agents

Built to be driven by an agent.

One credential, limited to the scopes the owner grants, every action audited. Remote MCP or plain JSON, same tools.

Start here

Give your agent the brief. It creates the account for a new owner, or asks an existing owner to approve a connect link. No copying of keys.

Read it

How an agent gets its credential

Path	When	How
Connect link default	The owner already has an account.	`POST /api/v1/agent/connect` → the owner opens `/connect/CODE`, reviews access and approves → the agent polls and receives the credential once.
Signup by the agent	The owner has no account yet.	`POST /api/v1/agent/signup` with the owner's email → invite email → the owner confirms and approves the proposed app → `draft_redeem`.
OAuth 2.1	MCP clients that can open a browser.	Point the client at `https://launchbase.build/mcp`; it registers, runs PKCE, the owner narrows scopes on the consent page.
Dashboard credential	You prefer to paste a key.	Agents & API → create with scopes, optionally bound to one app → `Authorization: Bearer lb_agent_…`.
Invite code	Pre-authorized automation with a budget.	Connections → one-time code with scopes and spend limit → `POST /api/v1/agent/redeem`.

What an agent can never do

Complete a payment, a top-up or a domain purchase: those come back as a link for the owner.
Grant itself permission to remove apps or services. Only you can change app protections; switching apps needs no approval.
Delete an app or turn off a component that holds data: it sends you to a page where you type the app name to confirm.
See provider master credentials or read a stored key back.
Reach another account: foreign ids answer 404.
Manage other agents or change account settings without the agents:manage role, which only humans have.

Scopes are listed under Security and data.

Entry points

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": { … } }

{ "mcpServers": { "launchbase": { "url": "https://launchbase.build/mcp",
    "headers": { "Authorization": "Bearer lb_agent_…" } } } }
// or leave headers out and let the client run the OAuth flow the server advertises

GET https://launchbase.build/api/v1/discovery      # endpoints and current status
GET https://launchbase.build/api/v1/guide          # deploy contract: stacks, port, health, limits
GET https://launchbase.build/api/v1/catalog        # components, regions, plans, features
GET https://launchbase.build/llms.txt

Tools

Apps, releases and logs; domains (attach or buy); email; payments; GitHub; usage; exports. See the REST reference for HTTP endpoints and request examples. MCP tools may use different input names. Errors carry a next step and an actor: anything marked owner is the human's job.