Skip to main content
An API key is a secret that identifies you. It is personal. It reaches the projects you can already open in the dashboard, and nothing more. Every key starts with rk_live_.

​
Create a key

1

Open the keys page

Open API keysClick Create an API key.
2

Fill in the four fields

3

Copy the key

It is shown once. If you lose it, revoke it and create a new one.

​
Send it

Put the key in the Authorization header of every request:

​
Permissions

A call that needs a permission the key does not have gets 403 SCOPE_MISSING. Permissions can only narrow what your seat on the project allows, never widen it.

​
Connected apps

MCP clients such as ChatGPT, Claude, Cursor and Codex do not use a pasted key. You sign in to Radarkit from the app and click Allow. That creates a key for the app, named after it, with the permissions you ticked. It appears on the keys page as a connected app and works exactly like any other key. Click Disconnect there to end the connection. See MCP setup.

​
Who can create keys

  • Project owners and admins on an active paid plan.
  • Editors cannot create keys.
  • Free accounts cannot create keys.
Every call on a project is charged to that project’s owner, whichever team member’s key made it. The ledger in Settings, API usage records who made each call.
Send the key only in the Authorization header. A key in the URL is refused with 400 KEY_IN_QUERY. Never put a key in browser code or a public repository. If a key leaks, revoke it on the keys page. Revoking is instant and cannot be undone.