Skip to main content
Use AI agent signup to create a bead account without a pasted API key, a card, or a human sign-in. The machine-readable walkthrough is bead.run/auth.md. For an agent that operates bead from your editor, see Use from your coding agent. For agents running inside a machine, see Run coding agents.

​
Start

bead signup --agent selects the same enrollment path explicitly. MCP clients can use account_create; the native enrollment endpoint is POST /v1/signup.

​
What the agent does

The CLI saves a signup ID, possession secret, and private delivery key before enrolling. It solves the server’s proof of work and decrypts the delivered account key locally. The result prints the organization, credential file, and trial metadata. It does not print the key. Keep both the private signup state and credential file. If the challenge expires or the reply is lost, retry bead signup with the same state. Completed enrollment returns the same organization and grant. Do not create a second signup to recover a missing reply. If the credential destination already exists, use that account. For a deliberately separate account, select a fresh private BEAD_API_KEY_FILE before signup.

​
Trial

Agent signup can receive trial credit. Check bead balance for your grant and expiry. The grant is once per organization and is not redeemable for cash. Read Agent trial credit for resource limits and paid activation. Human GitHub signup starts with zero credit. Claiming an agent workspace adds no credit and keeps trial restrictions.

​
Let a human claim the workspace

With an admin-scoped credential:
Send the returned private link to the intended human. They sign in at the dashboard and confirm ownership. The link is single use and expires after 30 minutes. It grants account ownership, so keep it out of public logs and tickets. See Account ownership and members.