Amba

Getting Access

Amba signup is open and self-serve, with no invite code needed. Where an optional invite code goes (API, MCP, CLI, console), what SIGNUPS_CLOSED, INVITE_REQUIRED, and INVITE_INVALID mean if signup is ever limited, and how to request access.

Amba signup is open and self-serve. Anyone can create an account from the API, MCP, the CLI, or the console, and no invite code is needed. Login, token refresh, PAT rotation, and the projects you already have work as before.

Signup modes

Amba sets one signup mode for the whole platform. The current mode is open. Signups can switch to invite_only or closed at any time; signup tells you which mode applies by its answer.

ModeNew accounts
openAnyone can sign up. An invite code is optional.
invite_onlyNeed a valid invite code.
closedNobody can sign up. Invite codes are refused in this mode too.

In invite_only and closed, creating projects is limited too. An account created with an invite code can create projects right away.

Daily project capacity for unproven accounts

In open mode, every signup gets its PAT and its first project at once: the API, MCP (amba_developer_signup), the CLI and the console page work the same way. Accounts whose owner has not yet proven control of the inbox draw those projects from a small daily capacity slice. Within that slice, each network and each company or custom email domain gets a few projects a day; addresses at large public mail providers share the slice through their network's limit. A signup with an invite code draws on the main pool.

When the slice is spent for a signup, the account is still created and keeps its PAT. Signup returns project_unavailable in place of project, with details.reason: "inbox_proof_required" and the ways to prove the inbox, and the account gets its first project once the owner proves it:

  • Claim: amba_developer_claim { "email": "<owner email>" } (MCP), amba claim <email> (CLI), or POST /v1/auth/developer/claim with the PAT. The owner opens the emailed link and presses Confirm.
  • Emailed sign-in code: when the account already uses the owner's real address, POST /v1/auth/developer/otp/request with { "email" }, then POST /v1/auth/developer/otp/verify with { "email", "code" }.

Then create the project with amba_projects_create (or rerun npx -y @layers/amba init). An unproven account that already has a project draws its next projects from the same slice; when the slice is spent, creating a project returns 503 PLATFORM_CAPACITY with details.pool: "unproven" and the same ways to prove the inbox. Proven accounts draw on the main pool.

Invite codes

An invite code is optional while signup is open. A code that is sent must still be valid, so drop a mistyped or expired code and sign up without one.

A code is AMBA- followed by four groups of four letters and digits, for example AMBA-7KQ2-M9XD-4TNB-HR3W. Case, spaces, and dashes are ignored, so a code pasted from an email works however it got wrapped. A code usually works once and may expire; the invite email gives the expiry date when there is one.

The code is spent only when the account is actually created. A signup that fails for another reason (for example 409 EMAIL_EXISTS) leaves the code usable.

Pass the code

SurfaceWhere the code goes
APIinvite_code in the body of POST /v1/auth/developer/signup
MCPinvite_code argument on amba_developer_signup (and amba_affiliate_signup)
CLInpx -y @layers/amba init --invite <code>. The headless signup also reads AMBA_INVITE_CODE.
ConsoleThe Invite code field on app.amba.dev/signup. The link in your invite email (https://app.amba.dev/signup?invite=<code>) fills it in, and Sign up with GitHub carries it.
curl -X POST https://api.amba.dev/v1/auth/developer/signup \
  -H 'Content-Type: application/json' \
  -d '{ "email": "you@company.com", "password": "at-least-8-chars", "invite_code": "<your invite code>" }'
amba_developer_signup({
  "email": "you@company.com",
  "password": "a-strong-password",
  "invite_code": "<your invite code>"
})

When signup is refused

While signup is open, the only 403 is INVITE_INVALID, for a sent invite code that is not valid. The other refusals occur only while signups are invite_only or closed. Each refusal is a 403 in the standard error envelope, with the request-access link in details:

{
  "error": {
    "code": "INVITE_REQUIRED",
    "message": "Amba signups are invite-only right now. Sign up again with an invite code (invite_code), or request access at https://app.amba.dev/request-access.",
    "details": {
      "request_access_url": "https://app.amba.dev/request-access",
      "request_access_endpoint": "POST /v1/auth/developer/waitlist"
    }
  }
}
CodeMeaningWhat to do
INVITE_REQUIREDSignups are invite-only and the request had no code.Retry with invite_code. No code yet? Request access.
INVITE_INVALIDThe code is mistyped, expired, revoked, or already used.Retry once without invite_code. If that answers INVITE_REQUIRED, request access.
SIGNUPS_CLOSEDNew accounts are closed for now, with or without a code.Request access and wait for the invite email.

Coding agents: sign up without invite_code unless the human gave you one. If a code answers INVITE_INVALID, sign up once more without it; if that answers INVITE_REQUIRED, treat the human as having no code. On INVITE_REQUIRED, ask the human for the invite code from their email and call signup again with it. If they have no code, or the answer is SIGNUPS_CLOSED, request access with the human's own email, tell them the code arrives by email, and stop. Never invent codes.

Request access

Fill in the form at app.amba.dev/request-access, or call the API:

curl -X POST https://api.amba.dev/v1/auth/developer/waitlist \
  -H 'Content-Type: application/json' \
  -d '{ "email": "you@company.com", "note": "Building a habit tracker in Expo" }'

note is optional (the first 500 characters are kept). Every well-formed email gets the same 200 { "data": { "ok": true } }, and asking again for the same address is safe. The endpoint is rate-limited per IP. Full reference: POST /auth/developer/waitlist.

The invite email

When Amba grants access to an address that requested it, it sends an invite email. The email contains:

  • Your invite code.

  • A signup link with the code filled in (https://app.amba.dev/signup?invite=<code>).

  • A one-line prompt to paste into your coding agent:

    Read https://amba.dev/llms.txt and integrate Amba into this app. Sign up with invite code AMBA-7KQ2-M9XD-4TNB-HR3W.
  • The terminal form: npx @layers/amba init --invite <code>.

  • The expiry date, when the code has one.

Paste the prompt into your agent and it signs up with the code and wires Amba into your app.

Existing accounts

Accounts that already exist sign in as before: the console, amba login, or amba_developer_login. Their projects keep running. If access is limited and creating a new project answers 403 SIGNUPS_CLOSED, the account is not cleared to create projects. An invite code clears it: redeem the code on the signed-in account with POST /v1/auth/developer/redeem-invite { "invite_code": "<code>" } (developer Bearer). No code yet? Request access as above, or contact support@layers.com.

On this page