On Belay

Getting started

Add your Anthropic key. Connect Claude. Invite your team. Point everyone in the same direction.

Get On Belay running in five steps: add your Anthropic API key, connect Claude, invite your team, create functional groups, and set Claude roles. You set it up once, and every Claude session your team opens inherits it — nobody has to re-explain your org to Claude again.

New organizations start on a 14-day free trial with full access. Set things up and use them for real before you choose a plan. Nothing is locked behind a paywall during the trial.

1. Add your Anthropic API key

On Belay runs agents and fieldsets on your own Anthropic API key — you pay Anthropic directly for model usage. A valid key is required before agents can run, so this is the first thing to set up.

Go to Dashboard → Settings → Claude, paste your key, and save. Get a key at console.anthropic.com → Settings → API Keys. We check the key with Anthropic before saving it, and it's encrypted before storage. See Plans, trial & billing for how this relates to your On Belay plan.

2. Connect Claude

On Belay works with Claude.ai, Claude Desktop, and Claude Code. The browser clients connect over an OAuth flow — no manual token copying. Claude Code uses a personal access token you generate once.

Your MCP URL is the same everywhere:

https://app.onbelay.ai/api/mcp

Claude.ai

Go to claude.ai/settings/connectors, click +, name it On Belay, and paste the MCP URL. Save and follow the sign-in prompt. Once authorized, On Belay's tools are available in every Claude conversation.

Claude Desktop

In Claude Desktop, open Settings → Connectors, click the + button, and paste the same MCP URL. Claude Desktop opens a browser to sign in and authorize. No config file, no manual token.

Claude Code

Claude Code uses a personal access token. In On Belay, go to Dashboard → Settings → Claude → Claude Code and click Generate. Copy the command shown — it comes pre-filled with your token:

claude mcp add --transport http onbelay https://app.onbelay.ai/api/mcp --header "Authorization: Bearer <token>"

The token is shown once. Run the command, then run claude and confirm the connection with /mcp.

For the full setup of each client, see Connecting Claude (MCP).

3. Invite your team

Add your team so everyone connects their own Claude and inherits the right context.

Go to Dashboard → People (admin only), enter their email in the Invite by Email field, and click Send invite. They get an invite link and sign in with Google or with an email and password. The first person to accept an invite into a new org becomes its admin.

There are two org roles:

  • Admin — manages groups, integrations, people, the plan, and settings.
  • Member — connects Claude and gets context for the groups they belong to.

You can change a person's role and assign them to groups any time from the People page.

4. Create functional groups

Functional groups are the core unit of On Belay. A group is a team — like Marketing, Engineering, or Finance — and it bundles everything Claude needs to work for that team: a Claude role, a strategy, people guidelines, integration access, and members.

Go to Dashboard → Groups → New group. Give the group a name and a short description. A person can belong to more than one group, and Claude sees the combined context from all of them.

To add people, open the group, go to the Members tab, search by name or email, and add them. Removing a member revokes that group's context and integration access on their next tool call.

For everything a group holds — all five editor tabs and per-operation permissions — see Functional groups & permissions.

5. Set Claude roles

Each group has a Claude role: plain-text instructions that shape how Claude behaves for everyone in that group. Use it to set the team's context, priorities, communication style, and any standing instructions.

You are assisting the Marketing team at Acme Co. This team manages paid acquisition, content, and brand. Always tie recommendations back to CAC and conversion. Tone: direct, data-driven.

Open a group and click the Claude Role tab to edit it. Changes take effect on the next call to get_my_context or get_group_context — no redeploy, no reconnect.

A group can also carry a Strategy (the team's goals and priorities) and People Guidelines (how Claude should treat the people on the team). Both ride along in the context Claude loads. See Core concepts for how these pieces fit together.

Recommended: connect Microsoft Clarity

The setup guide includes one recommended step that isn't required: connecting Microsoft Clarity. Nothing else in setup waits on it, and you can come back to it any time.

Clarity is where session replays, rage clicks, and dead clicks come from — behavioral friction data no other source gives you. It feeds the Website Optimization Agent and the friction signals on your dashboards.

Most of the work happens on Microsoft's side, which is why it isn't a blocking step:

  1. Create (or open) a project at clarity.microsoft.com as a project admin.
  2. Add Clarity's tracking script to your website. Clarity needs to be collecting on your site before it has anything to export.
  3. In Clarity, go to Settings → Data Export → Generate new API token, name the token (4–32 characters; letters, numbers, and -_. only — no spaces), and copy it. It's shown only once.
  4. In On Belay, go to Dashboard → Integrations, add Microsoft Clarity, and paste the token.

Clarity's export API is rate-limited to 10 requests per project per day, returns only the last 1–3 days of data, and caps responses at 1,000 rows.

Next steps

Need a hand getting your org set up? Reach us at hello@onbelay.ai and we'll walk you through it.