Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Emailchaser 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%2Femailchaser.com%2Femailchaser" | shStep 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%2Femailchaser.com%2Femailchaser" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Emailchaser API.
Build and run cold email campaigns with multi-step sequences and schedules
Find leads in the contact database and import them into a campaign
Connect SMTP and IMAP sender emails and track their warm-up and DNS health
Verify email lists and read inbox-placement and deliverability insights
Work with leads, replies, and AI reply drafts across a workspace
GET STARTED
Run autopilot campaigns with approval gates and register webhooks
Patterns agents use Emailchaser API for, with concrete tasks.
★ Agent-run cold outreach campaign
An agent plans a campaign from a website, launches it, attaches warmed-up sender emails, and sets the sending schedule, then monitors performance stats as replies come in. Each operation is discovered through Jentic by intent, so the agent goes from plan to live campaign without reading the reference docs.
Plan a campaign from a website, launch it, attach a sender email, set the schedule, and read its stats
Lead sourcing and verification
Fill a campaign with qualified prospects by searching the contact database against an ideal customer profile, importing matches, and verifying their email addresses before sending. An agent can size the audience, import leads, and run a verification job to protect deliverability.
Search the contact database for an ICP, import matching leads into a campaign, and verify their email addresses
Deliverability monitoring
Protect sending reputation by reading inbox-placement runs, sender reputation, and a sender email's DNS vitals and warm-up status. An agent can watch deliverability insights and pause sending when placement drops.
Read inbox-placement insights and a sender email's DNS vitals, and pause a campaign if placement falls
Reply handling
Keep conversations moving by listing replies, reviewing a lead's conversation, editing an AI reply draft, and sending it. An agent can triage incoming replies and mark meetings as booked on the lead.
List new replies, open a lead's conversation, edit the AI reply draft, send it, and mark a meeting booked
114 endpoints — the emailchaser api automates cold email outreach, covering campaigns, multi-step sequences, leads, sender emails, replies, and webhooks.
METHOD
PATH
DESCRIPTION
/campaigns
Create a campaign
/campaigns/{id}/stats
Get campaign performance stats
/campaigns/{id}/sequence
Replace a campaign's sequence
/lead-finder/imports
Import people from the contact database into a campaign
/email-verification/jobs
Verify a list of email addresses
/replies
List replies
/sender-emails
Connect an SMTP/IMAP sender email
/inbox-placement/insights
Read deliverability insights
/campaigns
Create a campaign
/campaigns/{id}/stats
Get campaign performance stats
/campaigns/{id}/sequence
Replace a campaign's sequence
/lead-finder/imports
Import people from the contact database into a campaign
/email-verification/jobs
Verify a list of email addresses
/replies
List replies
/sender-emails
Connect an SMTP/IMAP sender email
/inbox-placement/insights
Read deliverability insights
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Emailchaser API by hand means handling its bearer key and its read or read_write scopes, keeping credit topped up for the operations that spend money, and sequencing campaign, lead, and sender-email calls yourself. Through Jentic you install once, import the Emailchaser API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Emailchaser puts the campaign id in the URL path (/campaigns/{id}), so a rule can pin your agent to one campaign and the operations you pick. You choose the operations it may call, so spending operations like buying credits or ordering domains are not included unless you add them.
Credential isolation
Your Emailchaser 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 'create a cold email campaign' or 'find leads for an ICP', and Jentic returns the matching Emailchaser operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Emailchaser API through Jentic.
What authentication does the Emailchaser API use?
Per its OpenAPI spec, the Emailchaser API authenticates with a bearer API key, created per workspace, that is either read-only (read) or read and write (read_write). A small set of public marketing endpoints need no key. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's context.
Can I create a cold email campaign with the Emailchaser API?
Yes. The campaign operations create a campaign, set or replace its multi-step sequence, attach sender emails, set the schedule, and launch or pause it, and a stats operation reports performance as replies come in.
What are the rate limits for the Emailchaser API?
The OpenAPI spec does not state request rate limits; several operations instead gate on your credit balance and spend money when called. Check the Emailchaser documentation at https://www.emailchaser.com for current limits and credit costs.
Is there an Emailchaser MCP server?
You don't need an MCP server to give your agent the Emailchaser API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the campaign, lead, and deliverability operations it needs.
Can I limit what my agent is allowed to do with the Emailchaser API?
Yes. Because Emailchaser carries the campaign id in the URL path, you can pin a rule to one campaign and allow only the read and sequence operations, so the agent can run and report on that campaign. Spending operations such as buying credits or ordering domains are left out unless you add them, and every call the agent makes is logged.
How do I launch a campaign through Jentic?
Search Jentic for 'create a cold email campaign', and it returns the matching Emailchaser operations with their input schemas; your agent creates the campaign, sets its sequence, and launches it. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Automate cold email outreach: build and run campaigns and sequences, source and import leads, connect and warm up sender emails, verify lists, read deliverability insights, and handle replies and AI reply drafts.
Use for: Create a cold email campaign with a multi-step sequence, Find leads matching an ideal customer profile, Import people from the contact database into a campaign, Check a campaign's performance stats
Not supported: Does not run paid ads, send SMS, or host a sales CRM pipeline. Use for cold email outreach, deliverability, and lead sourcing only.
The Emailchaser API automates cold email outreach, covering campaigns, multi-step sequences, leads, sender emails, replies, and webhooks. An agent plans and launches campaigns, finds and imports leads from the contact database, connects SMTP and IMAP sender emails and tracks their warm-up and DNS health, verifies email lists, and reads inbox-placement and deliverability insights. It also runs autopilot campaigns with approval gates and manages ideal customer profiles, credits, and workspace members.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>