canonical: https://jentic.com/apis/emailconsul.com/main

# Emailconsul API

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.

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

## Scope

Does not handle SMS, push notifications, or CRM contact management. Use for email deliverability monitoring, list verification, and inbox placement testing only.

## Capabilities

- 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

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

Example prompt: 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.

Example prompt: 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.

Example prompt: Create a seedlisting inbox placement test and check the sending IP and domain against blocklists

## Key endpoints

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

## Key resources

- **DMARC** — Aggregated and timeseries DMARC reports per domain
- **List cleaning** — Submit and verify lists of email addresses
- **Seedlisting** — Seed-list inbox placement tests and their results
- **Checkers** — IP, domain, DKIM, and DMARC validation and blocklist checks
- **Reputation sources** — Google Postmaster and SNDS reputation data, spam traps, and lookalike domains

## 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:** 36 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 32 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 24 / 100
  - Agent Usability: 43 / 100
  - Security: 55 / 100
  - AI Discoverability: 40 / 100
- **View full report:** https://jentic.com/apis/emailconsul.com/main/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 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 handling:** 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.
- **Discovery method:** 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

- **UserCheck** — UserCheck validates individual email addresses where Emailconsul also monitors deliverability and DMARC.
- **Postmark** — Postmark sends the transactional email whose deliverability Emailconsul then monitors.
- **Brevo** — Brevo runs email campaigns that Emailconsul's list hygiene and DMARC monitoring support.

## FAQ

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