Emailconsul API
36
AI ReadinessNon-Ready (F)36/100
Community OpenAPI document · agent-readyCommunicationsEmail DeliveryapiKey, bearer256 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Monitor DMARC and sender reputation, verify and clean email lists, run seed inbox placement tests, check blocklists, and pull Google Postmaster and SNDS data.
Use for: Monitor DMARC results for my sending domain, Verify a list of email addresses before a campaign, Run a seed-list inbox placement test, Check whether an IP is on a blocklist
Not supported: Does not handle SMS, push notifications, or CRM contact management. Use for email deliverability monitoring, list verification, and inbox placement testing only.
The Emailconsul API watches email deliverability and sender reputation: it aggregates DMARC reports by domain, pulls Google Postmaster and SNDS data, and checks IPs, domains, DKIM, and DMARC records against validators and blocklists. It verifies and cleans email lists, runs seed-list inbox placement tests, tracks spam-trap and lookalike-domain hits, and sets up tracking pixels and links with alerts. It is the monitoring layer that tells you whether your email reaches the inbox.
Install Jentic One Beta
Connect the Emailconsul API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Emailconsul 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.
1
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%2Femailconsul.com%2Fmain" | sh2
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%2Femailconsul.com%2Fmain" | 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.
Capabilities
What an agent can do with Emailconsul API.
Monitor DMARC with aggregated and timeseries reports per domain
Verify and clean email lists by submitting addresses
Run seed-list inbox placement tests and read their results
Check an IP, domain, DKIM record, or DMARC record against validators and blocklists
Pull Google Postmaster and SNDS reputation data for your domains
Set up tracking pixels and links and create deliverability alerts
Use Cases
Patterns agents use Emailconsul API for, with concrete tasks.
★ Agent-driven deliverability monitoring
An AI agent watches whether a domain's email reaches the inbox, pulling DMARC aggregates, Google Postmaster reputation, and blocklist status on a schedule and raising an alert when something slips. Because the API separates aggregated and timeseries DMARC views, the agent can report both the current state and the trend behind a sudden drop in placement.
Pull the aggregated DMARC count and Google Postmaster data for a domain and alert if its reputation drops
List verification before send
Sending to stale or invalid addresses hurts reputation. Emailconsul verifies and cleans a submitted list of addresses, so an agent can scrub a campaign list before it is handed to a sending platform, cutting bounces and protecting the domain's standing.
Submit a campaign list for verification and return only the addresses that pass as deliverable
Inbox placement and blocklist checks
Before a major send, teams want to know where mail lands and whether their infrastructure is flagged. The API runs seed-list inbox placement tests and checks IPs, domains, and authentication records against blocklists and validators, so an agent can confirm placement and clear reputation issues ahead of time.
Create a seedlisting inbox placement test and check the sending IP and domain against blocklists
Key Endpoints
256 endpoints — the emailconsul api watches email deliverability and sender reputation: it aggregates dmarc reports by domain, pulls google postmaster and snds data, and checks ips, domains, dkim, and dmarc records against validators and blocklists.
METHOD
PATH
DESCRIPTION
POST
/listcleaning/list
Add a list of emails for verification
POST
/seedlisting
Create a seed-list inbox placement test
GET
/checkers/ip/{ip}
Check an IP's reputation
GET
/checkers/domain/{domain}
Check a domain's reputation
GET
/checkers/dmarc
Check a DMARC record
GET
/dmarc/aggregated/count
Get aggregated DMARC stats by count
POST
/alerts
Create a deliverability alert
GET
/gpdomains
Get Google Postmaster data
POST
/listcleaning/list
Add a list of emails for verification
POST
/seedlisting
Create a seed-list inbox placement test
GET
/checkers/ip/{ip}
Check an IP's reputation
GET
/checkers/domain/{domain}
Check a domain's reputation
GET
/checkers/dmarc
Check a DMARC record
GET
/dmarc/aggregated/count
Get aggregated DMARC stats by count
POST
/alerts
Create a deliverability alert
GET
/gpdomains
Get Google Postmaster data
Jentic AI Readiness Score
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.
E
Emailconsul API
- Non-Ready (F)36/100
32
Foundational Compliance63
Developer Experience & Jentic Compatibility24
AI-Readiness & Agent Experience43
Agent Usability55
Security40
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
32
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: FSignals: 4
27%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
2%
Example Density
How richly the API is illustrated with examples.
76%
Example Validity
Percentage of examples that conform to their schemas.
74%
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.
24
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
41%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
53%
Summary Coverage
Coverage of summaries across operations/tags/info.
43
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: D-Signals: 1
43%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
55
Security
Trust, risk posture, and security compliance.
Grade: CSignals: 1
55%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
40
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: D-Signals: 1
40%
Descriptive Richness
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>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Emailconsul API by hand means managing its Authorization token and working across many report, checker, and seedlisting endpoints each with its own shape. Through Jentic you install once, import it from the API Directory, store the token once, and your agent calls it.
Permission scoping
Targets such as a domain or IP travel in the path or request body, so a rule bounds which operations your agent may call, such as the checker and DMARC reads. You choose the operations it may call, so alert creation and list submission are not included unless you add them.
Credential isolation
Your Emailconsul token 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 'check email deliverability' or 'verify an email list', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Emailconsul API through Jentic.
What authentication does the Emailconsul API use?
The Emailconsul API authenticates with a token in the Authorization header, declared in its OpenAPI spec as both an API key and a bearer scheme. Through Jentic the token is stored encrypted by your own Jentic One instance and injected when a call runs, so it never reaches the agent's prompt or logs.
Can I verify an email list before sending with this API?
Yes. The list-cleaning endpoint accepts a submitted list of addresses and verifies them, so an agent can scrub a campaign list and keep only deliverable addresses before handing it to a sending platform.
What are the rate limits for the Emailconsul API?
The OpenAPI spec does not specify rate limits, though it exposes API request statistics endpoints you can read to track your own usage. Check the vendor documentation at emailconsul.com for current plan limits.
Is there an Emailconsul MCP server?
You do not need an MCP server to give your agent the Emailconsul API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent monitors DMARC and reputation on demand.
Can I limit what my agent is allowed to do with the Emailconsul API?
Yes. Write a rule that allows only the checker and DMARC read operations, so the agent can inspect reputation and blocklist status but cannot create alerts, submit lists, or change settings, and every call it makes is logged.
How do I monitor DMARC with this API through Jentic?
Search Jentic for an intent like 'get aggregated DMARC stats' and it returns the matching operation with its input schema, then your agent calls it with the token Jentic injects at runtime. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED