API keys
Create scoped keys for the agent gateway — automation, the MCP server and the CLI.
Where keys live
Open Settings → API keys (Admin and above). Every key belongs to your organization and only reaches your organization's data.
Creating a key
Click Create key, give it a name you will recognize, and pick the scopes it may use — grant only what the automation needs. The list of scopes you are offered matches what your organization can actually use: the brand's product first, then any add-ons.
The secret is shown exactly once, right after creation (rcsk_live_…). Copy it
immediately and treat it like a password — it cannot be read back. You can revoke it
from the same screen at any time, and a revoked key stops working for good.
Using a key
Present it as a bearer token on the agent gateway:
Authorization: Bearer rcsk_live_…
The gateway serves /api/agent/* — templates, marketplace cloning, campaigns,
surveys, results, audiences, contacts and conversations, each gated by the scopes
you granted. A key minted in one environment will not work against another.
The MCP server and the CLI
The same key drives the published MCP server and the CLI (@rcs-campaigns/agent-toolkit
on npm): point them at your gateway URL, paste the key once, and an agent (Claude
included) can search, create, clone, submit and send through your organization.
Last reviewed September 12, 2026