AI agents & API
Published by Argorant
MCP, REST, CLI - Argorant for machines.
Connect Claude (and Claude Code)
The two-minute MCP setup.
Connect ChatGPT, Cursor, Grok & Grok Bot
Connector or API key - every client works.
The setup prompt
A setup prompt that checks which connection your runtime supports.
API keys and the REST API
Endpoints, auth, and rate limits.
The Argorant CLI
npx argorant - search, verify and export from the terminal.
The free start for agents
The free start for AI agents on Argorant: the 14-day trial gives every confirmed account 100 credits and 300 campaign emails, with the fair-use limits explained.
MCP tools, scopes and spending safety
What an agent can do, and what it can never do silently.
Set up Argorant in Claude (desktop and web)
The full connector walkthrough, with what to check when it does not appear.
Set up Argorant in Claude Code
Set up Argorant in Claude Code with one MCP command, then pair the CLI so counts, searches, reveals and exports run fast from the terminal with your own API key.
Set up Argorant in ChatGPT with a connector
The MCP path, and which ChatGPT plans expose it.
Use Argorant in ChatGPT without a connector
When a configured HTTP action or terminal can use your personal key.
Set up Argorant in Codex
Set up Argorant in Codex: connect through the MCP server where the runtime supports it, otherwise use the REST API or the CLI with your own Argorant API key.
Set up Argorant in Cursor
Add the MCP server, or paste the setup prompt and let Cursor configure itself.
Set up Argorant in Grok
Set up Argorant in Grok with the OAuth MCP connector or a personal API key, then ask population questions that Grok answers from the live B2B contact dataset.
Set up Argorant in Grok Build
Set up Argorant in Grok Build, xAI's terminal coding agent: over MCP where enabled, otherwise REST with a bearer key, two minutes from install to your first count.
Set up Argorant in Grok Bot
Always-on teammates with a real data layer and a hard budget.
Build your own agent on Argorant
Custom runtimes: which surface to pick and how to shape the loop.
The authorization window, explained
What that sign-in pop-up is, why PKCE, and why some clients redirect to cursor://
The setup prompt, line by line
What each instruction in the copied prompt does, and why it is written that way.
REST: GET /api/mcp/account
Identity, scopes and daily quota. The call every agent should make first.
REST: GET /api/mcp/people/count
Free market counts. The endpoint you should call ten times before spending once.
REST: GET /api/mcp/people/preview
Free redacted previews. See the actual people before you pay for them.
REST: GET /api/mcp/people/reveal
The paid Argorant REST endpoint GET /api/mcp/people/reveal: one credit per contact returns name, title, company, work email, phone and LinkedIn URL inline.
REST: POST /api/mcp/exports/create
Create a verified CSV export job and get a job id back.
REST: export status, download and batches
Polling a job, fetching the CSV, and handling exports above 50,000 rows.
REST: company endpoints
Company counts, company search, and who works at a given domain.
REST: POST /api/mcp/email/verify and /verify/batch
Verify your own addresses, one at a time or in batches of 500.
REST: list endpoints
Save a filtered list, then check its size later. Both free.
401 and 403: authentication and scope errors
One means the key is wrong, the other means the key is not allowed.
402: payment required, and what to do about it
Nothing is broken. The account just cannot pay for what you asked.
429: rate limits and daily quotas
What a 429 means on the Argorant API: rate limits and daily quotas that scale with your tier, how to back off and resume, and why no request or credit is ever lost.
The CLI: install, shape and safety model
What npx argorant is, how it authenticates, and the one rule to internalize.
CLI: login, logout and where the key lives
Three ways to authenticate, and which one wins.
CLI: count and search
The two free commands you should wear out before spending anything.
CLI: company
Qualify a target account in one command, for free.
CLI: reveal
The command that spends credits inline. Read this before scripting it.
CLI: export, status, download and batches
Verified CSVs from the terminal, including exports above 50,000 rows.
CLI: verify, including CSV files
Use the Argorant CLI to verify email addresses you already own, one at a time or thousands from a CSV file, drawing on your check pool with free recent re-checks.
CLI: list create and list status
Save a segment as a filter set, check its size any time. Both free.
CLI: every filter and option
The complete flag surface, plus the two flags that behave differently than you expect.
CLI exit codes and what to do with each
Six codes that let an agent branch without parsing text.
CLI: campaigns (operator keys only)
What this command group is and why your key probably cannot use it.
Key rotation for agents
One key per agent, rotated on a schedule, revoked without drama.
Spending guardrails: instructions that keep an agent cheap
Copy-ready rules for your agent's system prompt, plus the limits enforced server-side.
API and MCP access need a plan or wallet credits
The Free tier is app-only. What unlocks machine access, and for how little.
Enrich: turn an email or a name into a full profile
One record in, one record out. The three modes, what each costs, and every error you can hit.
MCP connection and scope errors
MCP connection and scope errors on Argorant explained: approved connectors, OAuth authorization that expired, disabled actions, and the fix for each error message.
The connector daily quota
mcp_quota_exceeded: what it counts, and when it resets.
Too many reveals in a short window
The burst cap, why it exists, and the pattern that avoids it.
Your agent reports 'Export needs credits'
What the agent hit, and how to let it continue without babysitting.