Claude API Key
Run your products on your own Anthropic account, for the whole account or one workspace.
Settings → AI & connections → Claude API Key is where you add your own Anthropic (Claude) API key. It works on any plan, and only Admins can see it.
Two places to add a key
- Account key — the default for every workspace on the account, whichever Admin saved it.
- This workspace card — a key for the workspace you're in, which takes priority over the account key. Switch workspace first to set a key for a different one.
With no key, products run on Productised's key and use your credits.
To get a key, visit platform.claude.com/settings/keys in the Claude Console. Keys look like sk-ant-..., are encrypted before they're stored, and Productised staff can't view them.
Create the key for one workspace
When you create a key in the Claude Console, it asks which workspace the key belongs to. Choose one — Default workspace is fine unless you use others. (This is a workspace in your Claude Console, not a Productised workspace.)
Open Settings → API keys → Create key
In the Claude Console, give the key a name such as "Productised" and choose when it expires.
Leave Linked account as Not linked
The key then belongs to the workspace, not to a person, and keeps working if someone leaves your team. Linking it to yourself also works, as long as you still pick a workspace.
Pick a Workspace
This is the setting that matters. A key scoped to your whole organisation won't work in Productised.
If you see an error saying your key "isn't linked to a workspace" or "is not scoped to a workspace", the key was created for your whole organisation. Create a new key for one workspace as above, save it here, then delete the old one in the Console.
Why it matters: an organisation-wide key can run in any of your Anthropic workspaces, so Anthropic needs every request to say which one to bill. A key made for one workspace already knows, so nothing extra is needed.
What you get for it
- No credit limit. Your plan's included leads stop being spent, so nothing counts down and nothing runs out mid-campaign.
- Anthropic's rates, with nothing added. Usage is billed to your own Anthropic account at their list price. We don't re-bill it or mark it up.
- Your own capacity. Runs go through your Anthropic account's rate limits rather than sharing Productised' with every other customer.
- A shorter chain for a client who asks. The model runs on their Anthropic account rather than ours. It doesn't change where leads are stored — see Billing a client's AI to them for what it does and doesn't cover.
A key doesn't change which models run. The lead conversation uses Claude Haiku 4.5 while it's collecting answers and Claude Sonnet 4.6 for the Advisor either way, and the model picker on an AI Agent node is honoured whether or not you have a key.
Your key takes over straight away
A key isn't held in reserve for when your credits run out. From the moment you save it, every run it covers goes to Anthropic on that key, and your credits stop being spent at all — they sit unused, as a safety net for if you ever remove or rotate the key.
Anthropic bills you for that usage directly. It doesn't appear on your Productised invoice.
What your key covers
Product conversations and results — the chat and Advisor, AI Agents, scoring, and Standard, Page and Document results — run on your Anthropic account and use no credits. So do products you build through the Claude connector.
Brain, in-app Build with AI, voice input, AI Insights and Talking Points still run on Productised's services, at no credit cost.
If your key is rejected or runs out of credit, Productised doesn't switch to its own key. Owners and Admins get an alert, and a replaced key works straight away.
Seeing what it has cost
Your credit balance stops moving once a key is set, so it can't tell you how much you're using. Settings → Account & billing → Usage & cost shows what the AI cost to run in each workspace, and the Claude connector will report your runs and their cost on your own Anthropic account if you ask it about usage.
Your Productised API key
Looking for a key to call the Productised API from your own code? That's a different key, created in Settings → Advanced → API. See the API documentation.