api keys

api keys let paid users connect hold your voice to automations, ci, assistants, and the mcp server. keys are shown once.

updated may 3, 2026 api and mcp no images

quick answer

create one key per integration so it can be revoked without breaking everything.

use this for

connecting the rest api
setting up mcp
revoking a compromised key

steps

open api and mcp from the sidebar.
click new api key.
name the key after the integration.
copy the key when it is shown.
store it in a secret manager or environment variable.
revoke old keys when they are no longer needed.

details to know

each account can have up to ten active keys.
keys share account quota.
trial users can preview docs but cannot create keys until paid.
scopes control what an api key can call.

limits and edge cases

the raw key is shown only once.
never commit an api key to git or paste it into a public document.

ready to use the product instead of reading about it? open app