Keys
Agent keys let Cursor, Claude Code, ChatGPT (custom connectors), GitHub Copilot, Grok Bot, or any MCP client call the relay. They are separate from your dashboard login. An agent never gets your session cookie, and a bearer key cannot change your password or billing.
Create a key
On relay.idlerate.dev, open Connect a new agent (or the Agents section):
- Choose a paired machine. The key is attached to it, but it isn’t limited to it: the key can list and run models on every machine on your account.
- Give the key a label.
- Leave or clear scopes (see below).
- Create the key and copy it immediately — the full secret is shown once.
Keys look like idr_v1_xxxxxxxx_xxxxxxxx. The dashboard later shows only a short prefix.
Scopes
| Scope | What it allows |
|---|---|
models:list |
list_models |
models:run |
run_model |
jobs:read |
get_status, get_result |
jobs:cancel |
cancel |
keys:manage |
Create and revoke keys through the /keys API on the machine this key is attached to. Keys created that way only reach that one machine |
New keys default to all five. Clear keys:manage before creating a key if the agent should only run models. Giving an agent keys:manage means a stolen key can mint more keys until you revoke them.
Revoke a key
On the dashboard, revoke the key in one click. It stops working immediately. Create a new key for that agent afterward.
If you think a key was pasted into chat or committed to a repo, revoke it and make a new one. Never put a real key in documentation, screenshots, or issues.
Tips
- One key per agent or workspace is easier to revoke than one shared key.
- Pair a machine before creating a key — the form needs a machine to attach the key to. One key still covers all your machines; pass
machineonrun_modelto pick one. - Setup steps for each client: Connect your agent.