Browse documentation›
Build with Argorant.
Everything here is the how: endpoints, parameters, headers, commands, setup steps. If a mechanic appears anywhere else on the site, this is the copy that is kept current.
Get a key, count a market, pull a verified CSV. Ten minutes, start to finish.
How the key is sent, what it is allowed to do, how fast you may call.
REST, the CLI, or MCP. Same engine, same credits. Choose the one your stack speaks.
npx argorant count "fintech CFOs germany"
Three surfaces, one engine
The REST API, the CLI, and the MCP connector run the same search, verification, and export engine against the same workspace limits and credit balance. Nothing is available on one and missing on another. Pick whichever your stack already speaks.
REST API
The full HTTP surface. Same engine as the CLI and MCP.
CLI
Agents & MCP
Connect Claude, ChatGPT, or your own runtime over MCP.
Integrations
One setup guide per destination. These carry the endpoints and field mappings.
Connector review
For directory reviewers, not for building. Everything here is also stated on the pages above.
Create an account, then mint one at app.argorant.com/profile → API keys. Counts and previews cost no contact credits, so you can size a market before you spend anything.
