A setup prompt is a block of text you copy from Argorant and paste into your AI app. It tells the AI how to connect to your Argorant account, how to check that the connection really works, and how to behave once it does: look for free, ask before spending. You do not have to write any of it yourself.
Where to find it
Open AI connections in the Argorant sidebar (the same tabs are on argorant.com/ai-agents) and pick your AI app. Depending on the app you get one or two prompts.
| Prompt | Button | Which apps | What it does |
|---|---|---|---|
| Private setup prompt | Copy setup prompt | Codex and Claude Code (first view of the tab), Grok Bot | Contains a new personal key. Your AI connects itself through the Argorant command line, checks your account and starts the first search. |
| First-search prompt | Copy first-search prompt | Every app that connects through MCP, after you added Argorant and signed in | Checks your account, asks who you sell to and shows a free count and five masked examples. |
For Codex and Claude Code you create the key on the tab first with Create private key. Until then the prompt shows dots and the copy button stays grey. For Claude, ChatGPT, Cursor, Grok and other MCP apps you add Argorant in the app first; the first-search prompt is the last step.

The private setup prompt, in full
This is the prompt for Codex after you created a key. The key is replaced with dots here. Your copy has the real key.
Connect my Argorant account in Codex and help me find my next customers.
Private API key: ag_live_••••••••
I am sharing this freshly created key for this setup only. Do not repeat it in your response. Keep it out of URLs, browser storage, shared chats, logs, shell history and source files. Use a private secret or in-memory environment facility on the computer running this task. If that is unavailable, stop and explain the one private setup step you need from me.
Use this personal key for Argorant's CLI or REST API, not as an OAuth MCP token. Check my account with GET https://app.argorant.com/api/mcp/account and Authorization: Bearer using the private key. Do not create another account, rotate any key or overwrite an existing connection. Only report connected after the authenticated account check succeeds. If access is unavailable, explain the actual error and next step without changing my plan.
Then read https://argorant.com/docs/quickstart for the supported request schemas. Ask which companies, job titles and countries I want to reach. Use my answers, count the market and show a masked preview of five matches when my account allows it. Do not invent or silently drop filters. Ask for my explicit approval of scope, row limit and cost before revealing contacts, exporting, enriching or spending credits. Keep contact details in Argorant and return list or export links.Line by line
| Line | What the AI does with it |
|---|---|
| Connect my Argorant account in Codex... | Knows the goal and which app it runs in, so it uses the steps that fit. |
| Private API key | Gets the one secret it needs. The key belongs to your account and works for the command line and the REST API. |
| Do not repeat it... Keep it out of URLs... | Stores the key in a private environment variable instead of printing it, saving it in a file or putting it in a link. |
| If that is unavailable, stop and explain... | Asks you for one clear step instead of improvising a risky workaround. |
| Use this personal key for Argorant's CLI or REST API, not as an OAuth MCP token | Does not try to use the key for an MCP connection, which signs in a different way. |
| Check my account with GET .../account | Makes one real call to prove the key works before anything else. |
| Do not create another account, rotate any key or overwrite an existing connection | Leaves your setup as it is. No second account, no new keys, no replaced settings. |
| Only report connected after the authenticated account check succeeds | Never says "connected" on a guess. |
| Explain the actual error... without changing my plan | Tells you what went wrong in plain words and does not try to fix it with money. |
| Read .../docs/quickstart | Looks up the exact request formats instead of guessing them. |
| Ask which companies, job titles and countries... | Asks you about your market first. |
| Count the market and show a masked preview of five matches | Runs the two free steps, so you see the size and the kind of people before any cost. |
| Do not invent or silently drop filters | Tells you when a filter you asked for does not exist, instead of quietly searching something else. |
| Ask for my explicit approval of scope, row limit and cost... | Stops before every reveal, export or enrichment and waits for your yes. |
| Keep contact details in Argorant and return list or export links | Gives you links to Lists and Exports instead of pasting names and emails into the chat. |
The first-search prompt, in full
This is what Copy first-search prompt copies. It is the same for every app.
Help me find my next customers with Argorant. Check my account using the connection we just set up. Ask who I sell to, which roles I need and in which countries. Show a free count and a redacted preview of 5 matches using supported filters. Ask for approval of the scope, row limit and cost before spending credits. Keep contact details in my Argorant account and return list or export links.- "Check my account using the connection we just set up" makes the AI call the account tool first. That is your proof the connection works.
- "Ask who I sell to, which roles I need and in which countries" turns the first step into a short interview instead of a guess.
- "Show a free count and a redacted preview of 5 matches" keeps the first round free.
- "Ask for approval of the scope, row limit and cost before spending credits" is the spending rule for the rest of the chat.
- "Return list or export links" keeps contact data in your account.

Common mistakes
- Pasting the first-search prompt into a chat where Argorant is not connected. A prompt cannot install tools. Add Argorant in the app first, then paste it.
- Sharing the private setup prompt. It contains a working key. Paste it only into your own session. If it ended up somewhere else, delete the key under Settings, API keys.
- Editing out the approval line to save time. Without it, the AI may spend credits as soon as you ask for contacts.
- Pasting an old private prompt after you deleted its key. Create a new key and copy a fresh prompt.
After you paste it
The AI checks your account, asks about your market and shows a free count and preview. From there you decide what to reveal, save or export. You can add your own rules on top; the guardrails article has ready-made ones.
New accounts get a 7-day trial after email confirmation: 100 credits and 300 campaign emails, no automatic subscription; when it ends, campaigns pause and unused trial credits expire until a plan is added. The app, REST API, CLI and MCP share the same account and balance; connecting another client or creating an API key does not add a second grant. Existing balances and subscriptions are unchanged.