GGHL Command  Member Hub Design mockup
22px
DW
Command OSAdd your own Anthropic key
Command OSSetup

Add your own Anthropic key

The demo builder runs on your key, on your account. Ten minutes, and one trap that catches almost everybody.

Why it is your key and not ours

The demo builder turns a prospect's website into a working AI receptionist they can talk to. That is an AI request, and it bills to whoever owns the key. Command OS runs on your machine, your GoHighLevel account and your keys — so this one is yours too. Never send it to us, or to anyone. If you want help, share your screen and type it yourself.

The trap, and it caught Jerry

A key made without a workspace signs in perfectly and then refuses every single request. It is not a login failure. Anything that checks "is a key set?" will tell you everything is fine while nothing works, and the key itself is not allowed to tell you which workspace it needs. Jerry created one, saved it, and the demo answered every question with an error until it was caught.

Avoid it in one step: create the key on a workspace. A workspace key needs nothing extra and does not expire.

Do this once

  1. Go to platform.claude.com and sign in.
  2. Billing → add credit first. It is prepaid: with a zero balance the key exists and nothing runs. Turn on auto-reload with a low cap while you are there — a demo page on paid traffic with no cap is an open money tap.
  3. API keys → Create key. Name it something you will recognise. Set the workspace (Default is fine).
  4. Copy it once. The screen never shows it again.
  5. Put it where your Command OS setup asks for it. Never in a file, never in a chat window, never in an email.

Check it worked

Say this

Run a checkup.

Click the box to select it, then press ⌘C (or Ctrl+C)

The checkup asks Anthropic for real rather than checking that a key is present, so it can tell the difference between a key that works and a key that only looks like it does. If it names the workspace problem, go back to step 3 and make a new key — it takes a minute and the old one can be deleted.

What it costs

Roughly
Generating one demo6 cents
One question answered on a live demohalf a cent

Estimated from the published token prices against a real crawl, not measured. Around $20 of credit is a few hundred demos.

Before you start: the honest picture

This is the fourth thing that has to be true before a demo works, and it is fairer to say so now than to let you find them one at a time:

  1. A GoHighLevel plan that includes API access (their $297 or $497 tiers, not the $97 one).
  2. A Private Integration token from the sub-account.
  3. Claude running on your machine with GHL Command installed.
  4. An Anthropic key of your own, on a workspace, with credit.

Every one of them is a five-minute job. Together they are an afternoon, and knowing that up front is the difference between an afternoon and giving up in the middle of one.

A free way to try it first

There is a free Google key that allows about twenty questions a day. That is enough to build a demo and play with it, and not enough to put in front of a client. It is a good way to see whether this is worth the afternoon before you spend it.