Install Jentic One Beta

Connect the Argorant API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Argorant API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fargorant.com%2Fargorant" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fargorant.com%2Fargorant" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Argorant API.

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

GET STARTED

Start building with Argorant API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Argorant API for, with concrete tasks.

★ 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.

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.

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.

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

107 endpoints — the argorant api runs b2b outbound outreach end to end from a script or an agent.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Argorant API through Jentic.

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.

Argorant API

AI ReadinessAI-Aware (A-)71/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingMarketing Automationbearer107 EndpointsREST

For 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.

Use for: Search for marketing directors at SaaS companies in a country, Reveal the work email for a matched contact, Find a person's work email from their name and company domain, Verify an email list before sending a campaign

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

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

93%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

28%

Example Density

How richly the API is illustrated with examples.

98%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: B-Signals: 4

56%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

98%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

89%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

83%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B+Signals: 1

68%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Argorant API to your agent

Capabilities

Start building with Argorant API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Argorant API

Jentic AI Readiness Score

Argorant API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness