The Tool Keys tab in Platform Settings holds the shared pool of provider keys behind web search and web read. The pool serves every company; no client role can open or change it. Use this tab to add keys, label them, and take burned or retired keys out of rotation.
The table shows one row per key, with Provider, Key, Label, Status and Added:
| Column | Shows |
|---|---|
| Provider | Brave Search, Firecrawl or GitBook Docs. |
| Key | •••• plus the last four characters of the secret. The stored key is never shown. |
| Label | The annotation on the batch the key arrived in, when one was given. |
| Status | Enabled or Disabled. |
| Added | When the key entered the pool. |
Rows are ordered by provider, then oldest first. The platform picks among a provider's enabled keys
per request, so several keys per provider are normal; one burned key never stops the pool. The
table's export action writes every row, named provider-credentials.
Keys *).Each line becomes its own pool row, and the toast confirms {n} key(s) added to the pool.
Paste at least one key (one per line).batch 2026-07.Keys are write-once. After a batch is added, the pool never shows or reissues the secret, and the secret itself can never be edited. Rotate by disabling the old key and adding a new one.
{Provider} key ••••{secretHint}.Key updated.Labels are annotations only, up to 200 characters; they never affect which requests a key serves.
Disable {Provider} key ••••{hint}? and states the effect:Disabled keys leave the pool on the next request - the proxy stops load-balancing onto them. Keys are never deleted, so usage history stays attributable.
Enabled keys rejoin the pool and start serving requests again.Rotation is a two-step move, because a stored secret can never be edited in place:
The pool attributes every served request to the exact key row that served it. Replacing a stored secret would make that record wrong, so the pool forbids it.
Web tool calls need at least one enabled key. With none available, calls fail with a temporary unavailable error (503) until a key is added or enabled. The pool rebuilds itself after a platform restart, and every pool change rebuilds it at once, so the state clears without manual steps.
Up to 100. Each line becomes its own pool row; blank and duplicate lines are dropped.
No. A batch belongs to one Provider; run Add keys again for another provider.
Disable the old key, then Add keys with the replacement. The secret of an existing key can never be edited.
No. Disable takes a key out of service, and the row is kept so past requests stay attributable to it. Nothing in the pool is ever deleted.
•••• plus the last four characters of the stored key. That hint is the only part of a stored
secret the console shows.
On the next request: the key leaves the pool then, so it stops serving almost immediately.
Tool calls that need a key are refused with a temporary unavailable error (503) until a key is added or enabled. The pool rebuilds itself after a platform restart.
It found no usable key in the box. Paste at least one key, one per line; the message is
Paste at least one key (one per line).
The row you acted on could not be found, usually because the list was out of date. Open the tab again and retry.
It annotates the keys that arrived in one batch, for example batch 2026-07, and shows in the
Label column. A blank edit clears it; the limit is 200 characters.