Tools reach your Argorant account in one of two ways. Tools you set up yourself use an Argorant API key. AI apps connect by signing in to Argorant, with no key at all. Both work with the same account, credits, lists and campaigns.
| Tool | How it connects | Where to start |
|---|---|---|
| The CLI | An API key: npx argorant login, or the ARGORANT_API_KEY variable | Settings, API keys |
| The REST API | An API key in the header Authorization: Bearer | Settings, API keys |
| Postman | An API key as the Bearer token | Settings, API keys |
| Zapier, Make, n8n, Albato | An API key, pasted once when you connect Argorant in the tool | Settings, API keys |
| The browser extension | An API key, pasted once into the extension | Settings, API keys |
| Claude, ChatGPT, Cursor, Hermes, Manus and other AI apps | Sign in to Argorant and approve (OAuth). No key. | AI connections |
| HubSpot, Pipedrive, Google Sheets, Notion, Linear | Sign in to that tool and approve. No Argorant key. | Settings, Connected tools |
| Instantly, Smartlead, lemlist, PlusVibe | That tool's own API key, pasted under Connected tools | Settings, Connected tools |
Create a key
- Open Settings, API keys.
- Type a name that says where the key will live, for example
zapier,n8norbrowser-extension. - Click Create key, then Copy. The full key is shown only this once.
- Paste it into the tool. Keys start with
ag_live_.
One key per tool
A separate key for every tool costs nothing. You can revoke one without breaking the others, and its last used date tells you whether the tool still runs. More in Managing and revoking API keys.
AI apps sign in instead
Open AI connections in the app, pick your AI app and follow its steps. Manus and other apps without their own tab use Other MCP. You approve the connection on Argorant's own screen, so there is no key to copy and none to leak. To build a custom GPT action or your own agent code, you use a key after all: see Use Argorant in ChatGPT without a connector.
Keep keys private
- Never paste a key into a chat, a ticket or a shared document. A key in a chat does not connect anything.
- Each teammate creates their own key. Keys belong to the person who made them.
- If a key got out, revoke it and create a new one. See If an API key leaks.