Account setup and sign-in

Locus Pro separates your sign-in identity from the accounts and workspaces you can access. Self-serve signup creates a personal account. An evaluation or team invitation can add an enterprise workspace to the same identity. If you can access more than one, choose the active account after sign-in.

​

Choose a setup path

Personal signup does not create tenant API keys, end-user balances, markup, a widget, or an enterprise agreement. An evaluation also stays separate from any later commercial agreement: funding it adds prepaid credits but does not change its commercial status.

​

Create a personal account

1. Open Locus Pro signup.
2. Choose Email, Google, GitHub, GitLab, or Ethereum when that method is available.
3. Name the account when prompted. For email signup, enter the six-digit verification code. Ethereum signup also verifies a recovery email.
4. Add prepaid funds under Credits, enable capabilities under Tools, and connect an MCP client under Connections.

Only sign-up methods configured for the current environment appear. Google, GitHub, and GitLab signup use the verified provider identity. Ethereum signup proves wallet control with an EIP-4361 signature and binds the verified recovery email; it does not request a transaction, token approval, or access to funds. Confirmation provisions one personal account for the verified identity. Repeating confirmation or resuming after an interrupted browser session returns the same account instead of creating another. If email confirmation succeeded but setup did not finish, sign in and select Finish account setup. The public email/password API exposes the same sequence through POST /api/credits/auth/signup, POST /api/credits/auth/signup/confirm, and POST /api/credits/auth/signup/resend. After authentication, POST /api/credits/tenants/self-serve safely resumes personal-account provisioning. Use the API reference for request and response schemas.

​

Accept an invitation

Use the single-use link in the email rather than starting personal signup separately.

• An evaluation invitation creates the evaluation workspace described by that invitation.
• A team invitation joins an existing workspace as an admin, developer, billing member, or viewer.

Workspace invitations expire after seven days. Ask the workspace owner to resend an expired or revoked team invitation. Evaluation access is controlled by Locus.

​

Sign in to an existing account

The Create your Locus account screen and the Sign in screen behave differently. Choosing an external provider during signup creates a personal account. Choosing one during sign-in resolves an existing Locus identity; it does not silently create a second account. Password and passkey sign-in work directly. You can also manage linked methods from Account security:

• Google
• GitHub
• GitLab
• Sign-In with Ethereum (SIWE)

Google, GitHub, and GitLab sign-in resolve an existing verified-email identity and pin the provider subject after the first successful sign-in. Wallet sign-in requires that wallet to be linked from Account security first, even though wallet signup can create a new personal account with recovery-email verification. Disconnecting a method prevents future sessions through it but does not revoke sessions already issued; change the account password if you need account-wide session revocation. Accounts with managed SMS or TOTP MFA must use a password or passkey. External OAuth and SIWE intentionally do not bypass an enrolled second factor.

​

Plans and subscriptions

Personal tool usage is prepaid. One active OAuth-connected client is included at $0; optional Plus and Unlimited connection plans are monthly subscriptions and do not include usage credits. Some sales-led workspaces separately have an account-specific pricing tier, enterprise agreement, or recurring monthly credit subscription. See Commercial plans for the distinction.

​

Next steps