Atribu
Getting Started

Step 2 — Create your account

The one step in the whole path that a program cannot do for you, and the two ways to reach it.

There is no signup API, and that is deliberate

Account creation is a human act behind a captcha. Every other step below can be driven by a program; this one cannot, whichever track you are on.

  1. Go to atribu.app/signup.
  2. Enter your email and a password, and clear the Turnstile challenge.
  3. Confirm your email from the link we send you.

You land in the console with no workspace yet — that is step 3.

Free is a real plan, not a trial: $0, one ad account, no card. Growth and Agency are self-serve from the same signup (/signup?plan=growth, /signup?plan=agency); Enterprise talks to us first.

The bootstrap is the OAuth hand-off, exactly like connecting Gmail or Cloudflare. Your agent registers a client, builds an authorization URL, and hands that URL to its human — who creates the account inside that hand-off if they do not have one.

What your agent says
Open this to connect your Atribu account:
https://www.atribu.app/oauth/mcp/authorize?response_type=code&client_id=…

What the human sees, whether or not they already have an account:

  1. No account yet — the page sends them to sign in; an unrecognised email goes straight to signup with the pending authorization preserved. They confirm their email, and the confirmation link brings them back to the consent screen, not to a dashboard.
  2. The consent screen — the agent's name, the scopes it asked for as individual checkboxes, and the host its redirect points at. A user with no workspace is told so plainly: "You have no workspace yet — your agent will create one after you approve."
  3. Approve — the browser is redirected back to the agent with code and state.

The full sequence — dynamic client registration, PKCE, the token exchange, the refresh rotation — is the API quickstart. Do not duplicate it here; that page is the contract.

Come back when done

This is the whole hand-off pattern in miniature: hand over a URL, wait for a signal, continue. Steps 6, 7, 8, 11 and 12 use the same shape with an explicit object you can poll — see Hand-offs.

What you have at the end

An Atribu account with a confirmed email — and, on the agent track, an atb_user_… token that works on both the MCP endpoint and /api/v1.

Next steps

On this page