ArgorantDocs

Introduction

The shape of the Argorant API, what is free, what uses credits, and how the three surfaces relate.

One engine, three surfaces

Every capability exists once, on the REST API at https://app.argorant.com. The CLI and the MCP server call exactly those endpoints with your key or your OAuth session, so limits, permissions and credit balance are identical wherever you work.

SurfaceBest forAuth
RESTYour own code, pipelines, CRMsAuthorization: Bearer ag_live_…
CLITerminal, scripts, CI, coding agentsargorant login or ARGORANT_API_KEY
MCPClaude, ChatGPT, Codex and custom agentsOAuth sign-in on https://mcp.argorant.com/mcp

The workflow the API is built around

Find

Count and preview people by role, seniority, industry, country, company size or keywords. Free, unlimited within your daily quota.

Verify and keep

Reveal, enrich or export. Every address is checked live before it costs anything; only deliverable contacts are billed.

Reach

Turn a saved list into a campaign: write the sequence, attach your Google Workspace or Microsoft 365 mailboxes, launch. Argorant paces sends, warms mailboxes and collects replies.

Read and answer

The inbox endpoints give you every reply across campaigns, let you answer in-thread and set a verdict, including opportunity stages you define.

Path families

  • /api/mcp/* are the data endpoints (lookups, search, enrich, lists, exports, account). The name is historical; they are plain REST.
  • /api/v1/* are campaigns, inbox, reply statuses and mailboxes.
  • Everything returns JSON. Errors carry a detail string. Lists page with limit and offset.

The full OpenAPI document is at /openapi.json.

On this page