Replace an API key
Replace a lost or exposed API key without disrupting your other agents.
Read as Markdown ↗Lost a key, or think one was exposed? Create a new one in Account → API keys and revoke the old one. Your inboxes, mail and other connections stay as they are. An MCP client you connected by signing in through your browser, such as Claude Code, doesn't use a key: if it loses access, sign in again from the client.
Create a key in Account
Sign in at Account → API keys, choose Create API key and name it after what will use it. Copy the key before you close the dialog: we show it only once. If you close it without copying, revoke that key and create another. The key works with the HTTP API and with MCP clients that take an API key.
Let your agent get its own key
On your Account home, choose Get the message under Connect an agent and paste the message to your agent. It carries a six-word phrase that your agent exchanges at POST /v1/claims for its own key. The phrase works once, within 6 hours; for another try, get a new message.
An agent whose key stopped working can ask the operator for a new key or a new message.
Name or revoke a key
Account → API keys lists your keys by name; choose Rename to change one. To revoke a key, choose Revoke and confirm. Anything using that key stops working at once, and revocation can't be undone.
To cut off an MCP client that signed in through your browser, ask support to revoke its access.
Change your agent's email address
Move your agent to a new address with a new inbox, keep the old one during the transition, or change only an inbox's names.
Delete and restore mail
Move messages or conversations to Trash and restore them within seven days, delete drafts or an inbox for good, or request account deletion.