Self-serve signup

Most agents run against an account you already own: you set up your agent and it signs in through the browser. This guide is the other path, where an agent that has no account creates one itself, entirely from the terminal. Three commands take it from nothing to a stored, ready-to-use credential, without a browser or the dashboard. It is the same flow the MCP server exposes as the auth_signup, auth_verify_email, and auth_create_org tools.

You need the bird CLI installed. Signup and verification are region-agnostic and require no initial configuration. At the last step, pass --region (us1 or eu1) to create-org to choose where the account and its data live. No hostnames or environment variables are required.

bird auth signup creates the account and emails a six-digit sign-in code. It uses the same passwordless magic-link path as the dashboard, so the emailed code is all you need. Keep the email address for the next step.

bird auth signup you@example.com
# { "email": "you@example.com", "status": "code_sent" }

The six-digit code arrives by email, so it comes from outside the CLI: read it from the inbox. Pass it with the same email to bird auth verify-email, which signs you in and, for a brand-new account, returns a single-use onboarding_ticket.

bird auth verify-email you@example.com --code 123456
# { "onboarding_ticket": "...", "user_id": "usr_..." }

bird auth create-org consumes the ticket to create the first organization and workspace, then stores the minted credential so the CLI and the MCP server authenticate as the new account from here on. It is one-time: a second call returns 409. --region chooses where the account and its data live (us1 or eu1) and routes the call to that region; the CLI derives the host from it, so you do not set a URL.

bird auth create-org "Acme" --workspace-name "Production" --region us1 --onboarding-ticket <onboarding_ticket>

Confirm the credential works:

bird auth status   # authenticated: true, valid: true

The account is live and authenticated. The agent can now send email, manage domains, and everything else the CLI exposes, with no further setup.

Every step is self-describing and needs no credential, so an agent can plan the whole chain before sending anything. bird auth --help prints the ordered flow, --example prints a ready-to-edit request body, and --response-schema prints the fields each command returns.