canonical: https://jentic.com/apis/argorant.com/argorant

# Argorant API

The Argorant API runs B2B outbound outreach end to end from a script or an agent. It searches business contacts and companies by industry, title, country, and technology, reveals verified work emails and phone numbers, finds a single email from a name and domain, and verifies email lists before sending. It then writes campaigns with a personal line per contact, sends from connected Google Workspace, Microsoft 365, or SMTP mailboxes, and tracks replies in a unified inbox with follow-up sequences and a reply-status pipeline.

## For AI agents

Find and verify B2B contacts, then run outbound email campaigns end to end: search people and companies, reveal emails and phones, verify lists, write and launch campaigns, and answer replies from a unified inbox. Authenticate with a bearer key.

## Scope

Does not run paid ad campaigns, process payments, or send SMS messages. Use for B2B contact discovery and outbound email outreach only.

## Capabilities

- Search business contacts and companies by industry, title, country, and technology
- Reveal verified work emails and phone numbers for matched people
- Find one person's work email from a name and company domain
- Verify email lists before a send to cut bounces
- Write and launch outbound email campaigns with a personal line per contact
- Connect sending mailboxes from Google Workspace, Microsoft 365, or SMTP
- Read campaign replies and answer them in the same thread from a unified inbox

## Use cases

### Build and Verify a Prospect List

An agent searches Argorant for people who match an ideal-customer profile, reveals their verified work emails, and verifies the resulting list before any send. Argorant checks each email right before it is returned, so the agent builds a clean prospect list in one pass instead of stitching together a finder and a separate verification service.

Example prompt: Call GET `/api/v1/people/search` for the profile, POST `/api/v1/people/reveal` to get emails, then POST `/api/v1/verifications` to check the list

### Run an Outbound Campaign

An agent writes a campaign with a personal line for each contact, connects a sending mailbox, and launches the sequence, then reads replies and answers them in the same thread. Argorant handles the mailboxes, personalization, and reply tracking so the agent manages a full outbound motion through one API.

Example prompt: Call POST `/api/v1/campaigns` to create a campaign, POST `/api/v1/campaigns/{campaign_id}/launch` to send it, then GET `/api/v1/campaigns/{campaign_id}/replies` to read responses

### AI Agent Integration via Jentic

An AI agent reaches the Argorant API through Jentic without holding the bearer key itself. It searches by intent, receives the matching operation with its input schema, and executes the call with the credential injected at run time, so contact discovery and campaign steps slot into a larger agent workflow.

Example prompt: Search Jentic for 'find a work email', load the POST `/api/v1/email-finder/find` schema, and execute it with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/v1/people/search` | Search people |
| POST | `/api/v1/people/reveal` | Reveal emails and phones for people |
| POST | `/api/v1/email-finder/find` | Find a work email |
| POST | `/api/v1/verifications` | Start an email list check |
| POST | `/api/v1/campaigns` | Create a campaign |
| POST | `/api/v1/campaigns/{campaign_id}/launch` | Launch a campaign |
| GET | `/api/v1/inbox` | List conversations |
| POST | `/api/v1/inbox/{event_id}/reply` | Answer in the thread |

## Key resources

- **People and Companies** — Search, count, and reveal contacts and companies via `/api/v1/people/search`, `/api/v1/people/reveal`, and `/api/v1/companies/search`
- **Email Finder and Verification** — Find and verify work emails via `/api/v1/email-finder/find` and `/api/v1/verifications`
- **Campaigns and Inbox** — Create, launch, and track campaigns and answer replies via `/api/v1/campaigns` and `/api/v1/inbox`
- **Mailboxes** — Connect and manage sending mailboxes via `/api/v1/inboxes` and `/api/v1/inboxes/smtp`

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 71 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 98 / 100
  - Developer Experience & Jentic Compatibility: 69 / 100
  - AI-Readiness & Agent Experience: 61 / 100
  - Agent Usability: 83 / 100
  - Security: 60 / 100
  - AI Discoverability: 68 / 100
- **View full report:** https://jentic.com/apis/argorant.com/argorant/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Argorant by hand means managing its ag_live_ bearer key, sharing one credit balance across your tools, and connecting sending mailboxes yourself. Through Jentic you install once, import Argorant from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Argorant carries the campaign and contact ids inside each request, so a rule bounds which operations your agent may call. You choose the operations it may use, such as contact search and email finding, so sending operations like launching a campaign or ordering mailboxes are not included unless you add them.
- **Credential handling:** Your Argorant key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'find a work email' or 'launch an outbound campaign', and Jentic returns the matching Argorant operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Apollo** — Sales intelligence database with contact data and email sequences
- **Hunter** — Email finding and verification by domain
- **Salesloft** — Sales engagement platform for cadences and rep workflows

## FAQ

### What authentication does the Argorant API use?

The Argorant API authenticates with a bearer key in the Authorization header, per its OpenAPI spec, with keys shaped like ag_live_ for your account. The API, the command-line tool, and the vendor's MCP server share the same key and account. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never reaches the agent.

### Can I find and verify work emails with the Argorant API?

Yes. POST `/api/v1/email-finder/find` returns a single work email from a name and company domain, and POST `/api/v1/verifications` runs a list check so you can confirm addresses before sending. Argorant also checks revealed emails right before returning them to cut bounces.

### What are the rate limits for the Argorant API?

Argorant draws from one credit balance shared across the API, CLI, and MCP server rather than a fixed request ceiling, and the OpenAPI spec does not state request limits. Read the account endpoint for remaining credits, watch for HTTP 429 responses, and check Argorant's documentation for current limits.

### How do I find a work email with the Argorant API through Jentic?

Search Jentic for 'find a work email', and it returns the Argorant operation with its input schema. Load the schema and execute POST `/api/v1/email-finder/find` with the credential injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Is there an Argorant MCP server?

Yes, Argorant offers an official MCP server. You can also connect Argorant directly through Jentic: your agent gets the full 107-endpoint surface without loading another server's tool definitions into its context, your credential is injected at call time by your self-hosted instance instead of living in an MCP config, and your rules decide which operations the agent may call.

### Can I limit what my agent is allowed to do with the Argorant API?

Yes. Write a rule that allows only contact search, reveal, and email finding, so the agent can build a prospect list while sending operations stay off the table. Launching a campaign or ordering mailboxes is withheld until you add it, and every call runs through your own instance where it is logged for review.