Authentication and limits
Bearer API keys, the base URL, OAuth scopes for MCP, per-plan limits and what costs credits.
Base URL
https://app.argorant.comAPI keys
Sign in and mint a key at app.argorant.com/profile → API keys. Keys start with ag_live_, are shown once, and work on REST and the CLI. Name each key after the thing that uses it (zapier, ci, laptop) so you can revoke one without breaking the rest.
curl "https://app.argorant.com/api/mcp/account" \
-H "Authorization: Bearer $ARGORANT_API_KEY"{
"ok": true,
"email": "you@example.com",
"role": "owner",
"scopes": ["argorant:read_counts", "argorant:search_segments", "argorant:manage_lists", "argorant:create_exports", "argorant:unlock_contacts"],
"usage": { "counts_today": 12, "previews_today": 3, "reveals_today": 0 }
}The CLI reads the same key from argorant login or the ARGORANT_API_KEY environment variable.
MCP uses OAuth, not the key
MCP clients never see your API key. They sign in over OAuth 2.1 (authorization code with PKCE) against https://mcp.argorant.com/mcp and act under the same account with the scopes below. See Connect a client.
| Scope | Cost | Unlocks |
|---|---|---|
argorant:read_counts | Free | Counts, account state, campaign and inbox reads |
argorant:search_segments | Free | Coverage search and masked previews |
argorant:manage_lists | Free | Saved lists, campaign writes, launching, replying, reply statuses |
argorant:create_exports | Credits | Export jobs and list exports |
argorant:unlock_contacts | Credits | Reveal and person enrichment |
What costs what
| Action | Cost |
|---|---|
| Lookups, counts, previews, company coverage | Free |
| Reveal or export a contact | 1 credit per deliverable contact |
| Enrich a person you already have | 1 credit per match, misses free |
| Verify an address you own | 0.5 credit |
| Campaign emails | Included in the plan allowance, never credits |
Rate limits
Daily allowances per key are returned on every account call and on 429 responses. Bursts over 30 requests per second from one IP are throttled with 429 and a Retry-After header.
Permissions
A key inherits the permissions of the account that created it. A workspace member with outbound rights can run campaigns; a member without them gets 403 on /api/v1/campaigns. Owners see only their own workspace.