---
title: "API keys | Proxy Mail QA"
description: "Create a Proxy Mail QA API key for an agent, a script or a test suite: what it can do, where to keep it, and the permission to read saved passwords."
url: https://proxymail.qa/docs/api-keys
---

# API keys

In [app.proxymail.qa](https://app.proxymail.qa), open the project switcher → **Project settings** → **API keys** → **Create key**. A key works in that project only and can do what you can do there. It’s shown once: keep it in an environment variable such as `PROXYMAIL_QA_API_KEY`, never in code you share.

Tick **Can read saved passwords** only for keys that need to sign in as a test account again. You can switch it on or off later with **Allow reading passwords** or **Stop reading passwords** on the key, and each change is in the activity log. Every reveal is logged too: the key shows how often and when it last read a password, and owners and admins see each account’s password history (who revealed or copied it, when, and through the app, the extension, an agent or which key) in its details. Agents signed in through the browser never read passwords saved earlier.

AI apps that sign in by browser, such as Claude and ChatGPT, don’t need a key: see [MCP server](https://proxymail.qa/docs/mcp). Keys and connected apps are listed under **Project settings → API keys**, where you can revoke them at any time.

[Previous Set up your agent](https://proxymail.qa/docs/api.html) [Next MCP server](https://proxymail.qa/docs/mcp.html)