Create an Outbind account

How a person signs up for Outbind, or how an AI agent makes the account for them with the code Outbind emails, and gets a key to connect.

For AI agents: this page as MarkdownAll docs as Markdown

There are two ways to make an Outbind account. Both are free and need no card, and both start on the Free plan, which includes the MCP connection and every brain tool. Either way the person proves the email address is theirs with a code Outbind sends them.

The person signs up in the browser

Open app.outbind.ai/sign-up.
Choose Sign up with Google, or type a work email, press Email me a code and type the code from the email.
Answer the short set-up: their name, the company name and its website. It takes about two minutes.

Then they connect their assistant: see Connect over MCP. If they press Connect in their assistant before they have an account, Outbind's sign-in page opens with a Create an account link; after sign-up they press Connect again and then Allow.

This is the way for Claude and ChatGPT in the browser or desktop app.

An AI agent signs the person up

Agents that can make HTTP requests or run commands (Claude Code, Cursor, Codex, scripts) can make the account for the person and get a key in two calls.

1. Ask Outbind to email the person a code.

curl -X POST https://app.outbind.ai/api/v1/signup \
  -H "content-type: application/json" \
  -d '{"email":"jane@acme.com"}'

2. Ask the person for the 6-digit code from that email (it works for 10 minutes), plus their name and company name, then:

curl -X POST https://app.outbind.ai/api/v1/signup/verify \
  -H "content-type: application/json" \
  -d '{"email":"jane@acme.com","code":"123456","name":"Jane Doe","company":"Acme","timezone":"Europe/Madrid","app":"Claude Code"}'

The answer holds the key, shown once:

{
  "key": "ob_…",
  "new_account": true,
  "workspace": { "id": "…", "name": "Acme" },
  "access": "mcp_write",
  "mcp_url": "https://app.outbind.ai/api/mcp",
  "brain_api": "https://app.outbind.ai/api/v1/brain",
  "docs": "https://outbind.ai/docs/agents.md"
}

The key can draft and edit. Use it as Authorization: Bearer ob_… on the MCP server or the Brain API. Save it where the person keeps secrets, such as an OUTBIND_API_KEY environment variable, and never print it in a shared place. The person sees it in Settings, MCP and can revoke it there.

Next, call get_brain and then create_icp with the person's website, so every message knows who they sell to.

Rules for agents:

Only sign up the person you are helping, with their own email, and only when they asked for an account.
Ask for the code; never read their inbox to find it without their say-so.
If they already have an account, the same two calls give a key to their workspace (name and company aren't needed). An account with two-step sign-in on can't be reached this way: they connect with the Connect button instead.
name and company are checked before the code is used, so if one is missing you can ask and send the same code again.

Errors: 400 bad input or a wrong or expired code (fields says what), 403 an address or network Outbind won't take, or two-step sign-in, 429 too many tries (wait and try again later), 503 agent sign-up is paused (send the person to the sign-up page).

The outbind command line tool does both steps: outbind signup jane@acme.com emails the code and asks for it.

Teams and roles

One workspace per company. The person who makes it is its owner and can invite teammates in the app (Settings, Team) as:

Admin: everything an owner can do with the brain, including the ideal customer profile, team lessons and documents.
Member: every writing tool, prospect notes and their own writing habits.
Read only: can read the brain and prospects and sort replies. Can't connect apps.

The tools follow the person's role in the workspace, whatever their assistant asks for.

Connect over MCP