Agent keys

OAuth is the normal path and needs no key. Agent keys exist for the case OAuth cannot serve: a custom or self-hosted agent, running unattended, with no browser to complete an authorization screen.

Creating one

1. 1Open Agents in the dashboard.
2. 2Create a key and give it a name you will recognise later — the name is how you will decide what to revoke.
3. 3Scope it to specific sites. A key restricted to the sites it needs cannot touch the others.
4. 4Optionally set a monthly cap on that key, so one misbehaving agent cannot consume your whole plan allowance.
5. 5Copy the key. It starts with pb_live_ and is shown once — Pressbotics stores only a hash and cannot show it to you again.

A key is a credential. Put it in your agent's environment or secret store, never in source control, a prompt, or a chat message.

Scoping

• Keys can only be scoped to live, connected sites.
• One key per agent, not one key shared by everything. That is what makes Activity and revocation meaningful.
• The key never grants more than the rail itself can do — it cannot manage users, settings, plugins or themes.

Watching and revoking

Each key shows when it was last used. Every action recorded in Activity carries which key made it. Revoking a key takes effect immediately and does not touch anything already published. Your plan sets how many keys you can hold at once — see Plans and limits.

What can go wrong

• The key was copied with surrounding whitespace. Trim it.
• The key is revoked, or scoped to a site other than the one in the call. The call is refused; nothing partial happens.
• The key hit its own monthly cap. Raise the cap, or find out why the agent is publishing that much.