> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to Validity Everest

The Validity Everest connector lets your AI agent act in each user's Validity Everest account. Each user connects their own Validity Everest API key once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 65 tools.

**Authentication:** API Key
**Categories:** Marketing, Monitoring
**Tools:** 65: 54 read, 7 write, 4 destructive
**Users sign in with:** API key
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=EVEREST)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Validity Everest connection

   In **AgentKit > Connections**, create a Validity Everest connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'everest'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Validity Everest:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'everest_blocklist_listings_list',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "everest"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize Validity Everest:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="everest_blocklist_listings_list",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user opens the link once and enters their Validity Everest credentials there. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'everest_blocklist_listings_list',
  toolInput: {},
  connector: 'everest',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="everest_blocklist_listings_list",
    tool_input={},
    connection_name="everest",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `everest_blocklist_listings_list`

List Blocklist Listings · Read-only

List blocklist listings of your monitored IPs and domains.
Returns each listing with the item, blocklist, profile, listed and delisted dates, and links to related resources.
Use everest_blocklist_listings_list to see what is on a blocklist now (status current) or what was resolved. Use everest_reputation_profiles_list for per-profile issue counts.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `enddate` (`string`, optional): End of the date range, YYYY-MM-DD (or YYYY-MM-DD HH:MM:SS, UTC). Defaults to today. Example: 2026-10-31.
- `limit` (`integer`, optional): Results per page (default 500). Example: 500.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `startdate` (`string`, optional): Start of the date range, YYYY-MM-DD (a time can follow, YYYY-MM-DD HH:MM:SS, UTC). Defaults to 30 days ago. Example: 2026-10-01.
- `status` (`string`, optional): all, current (still listed) or resolved (delisted). Default all. Example: current. One of: `all`, `current`, `resolved`.

Example input: `{}`

### `everest_blocklists_list`

List Blocklists · Read-only

List the IP and domain blocklists Everest monitors.
Returns each blocklist with its ID, name, type (ip or domain) and description.
Use everest_blocklists_list to pick blocklist IDs for everest_reputation_profile_create. Use everest_blocklist_listings_list for your own listings.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `type` (`string`, optional): Only ip or domain blocklists. Leave empty for both. Example: ip. One of: `ip`, `domain`.

Example input: `{}`

### `everest_dmarc_domain_dkimdomains_list`

List DMARC DKIM Domains · Read-only

List DMARC data for a domain: each DKIM signing domain seen with volume and DKIM results.
Returns each DKIM signing domain seen with volume and DKIM results for the date range, paginated.
Use everest_dmarc_domain_dkimdomains_list to check which DKIM signatures align with the domain. Use everest_dmarc_domain_get for the domain's overview.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): The DMARC-monitored domain, without a scheme. Example: example.com.
- `classification` (`array`, optional): Only mail with these DMARC classifications: compliant, non-compliant, unauthenticated. Example: ["non-compliant", "unauthenticated"].
- `dkimdomain` (`string`, optional): Only mail with this DKIM domain. Example: mail.example.com.
- `dkimresult` (`string`, optional): Only mail with this DKIM result: none, pass, fail, softfail, temperror or permerror. Example: fail. One of: `none`, `pass`, `fail`, `softfail`, `temperror`, `permerror`.
- `enddate` (`string`, optional): End of the date range, YYYY-MM-DD (or YYYY-MM-DD HH:MM:SS, UTC). Defaults to today. Example: 2026-10-31.
- `forwarded` (`string`, optional): include or exclude forwarded mail. Forwarded mail with a valid ARC chain (arc=pass) had SPF or DKIM validated before forwarding. Example: exclude. One of: `include`, `exclude`.
- `ip` (`string`, optional): Only mail from this IP. Example: 192.0.2.10.
- `limit` (`integer`, optional): Results per page (default 100). Example: 100.
- `mailorigin` (`string`, optional): Only mail from this origin (sending service domain). Example: gmail.com.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `spfdomain` (`string`, optional): Only mail with this SPF domain. Example: mail.example.com.
- `spfresult` (`string`, optional): Only mail with this SPF result: none, pass, fail, softfail, temperror or permerror. Example: fail. One of: `none`, `pass`, `fail`, `softfail`, `temperror`, `permerror`.
- `startdate` (`string`, optional): Start of the date range, YYYY-MM-DD (a time can follow, YYYY-MM-DD HH:MM:SS, UTC). Defaults to 30 days ago. Example: 2026-10-01.

Example input: `{"domain":"<domain>"}`

### `everest_dmarc_domain_dkimresults_list`

List DMARC DKIM Authentication Issues · Read-only

List DMARC data for a domain: DKIM failures grouped by result and source.
Returns DKIM failures grouped by result and source for the date range, paginated.
Use everest_dmarc_domain_dkimresults_list to find DKIM problems. Use everest_dmarc_domain_get for the domain's overview.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): The DMARC-monitored domain, without a scheme. Example: example.com.
- `classification` (`array`, optional): Only mail with these DMARC classifications: compliant, non-compliant, unauthenticated. Example: ["non-compliant", "unauthenticated"].
- `dkimdomain` (`string`, optional): Only mail with this DKIM domain. Example: mail.example.com.
- `dkimresult` (`string`, optional): Only mail with this DKIM result: none, pass, fail, softfail, temperror or permerror. Example: fail. One of: `none`, `pass`, `fail`, `softfail`, `temperror`, `permerror`.
- `enddate` (`string`, optional): End of the date range, YYYY-MM-DD (or YYYY-MM-DD HH:MM:SS, UTC). Defaults to today. Example: 2026-10-31.
- `forwarded` (`string`, optional): include or exclude forwarded mail. Forwarded mail with a valid ARC chain (arc=pass) had SPF or DKIM validated before forwarding. Example: exclude. One of: `include`, `exclude`.
- `ip` (`string`, optional): Only mail from this IP. Example: 192.0.2.10.
- `limit` (`integer`, optional): Results per page (default 100). Example: 100.
- `mailorigin` (`string`, optional): Only mail from this origin (sending service domain). Example: gmail.com.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `spfdomain` (`string`, optional): Only mail with this SPF domain. Example: mail.example.com.
- `spfresult` (`string`, optional): Only mail with this SPF result: none, pass, fail, softfail, temperror or permerror. Example: fail. One of: `none`, `pass`, `fail`, `softfail`, `temperror`, `permerror`.
- `startdate` (`string`, optional): Start of the date range, YYYY-MM-DD (a time can follow, YYYY-MM-DD HH:MM:SS, UTC). Defaults to 30 days ago. Example: 2026-10-01.

Example input: `{"domain":"<domain>"}`

### `everest_dmarc_domain_geolocation_list`

List DMARC Geolocation · Read-only

List DMARC data for a domain: mail volume and DMARC results by country, region and city.
Returns mail volume and DMARC results by country, region and city for the date range, paginated.
Use everest_dmarc_domain_geolocation_list to see where mail claiming the domain comes from. Use everest_dmarc_domain_get for the domain's overview.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): The DMARC-monitored domain, without a scheme. Example: example.com.
- `city` (`string`, optional): Only mail from this city. Example: San Francisco.
- `classification` (`array`, optional): Only mail with these DMARC classifications: compliant, non-compliant, unauthenticated. Example: ["non-compliant", "unauthenticated"].
- `country` (`string`, optional): Only mail from this country (code or name). Example: US.
- `dkimdomain` (`string`, optional): Only mail with this DKIM domain. Example: mail.example.com.
- `dkimresult` (`string`, optional): Only mail with this DKIM result: none, pass, fail, softfail, temperror or permerror. Example: fail. One of: `none`, `pass`, `fail`, `softfail`, `temperror`, `permerror`.
- `enddate` (`string`, optional): End of the date range, YYYY-MM-DD (or YYYY-MM-DD HH:MM:SS, UTC). Defaults to today. Example: 2026-10-31.
- `forwarded` (`string`, optional): include or exclude forwarded mail. Forwarded mail with a valid ARC chain (arc=pass) had SPF or DKIM validated before forwarding. Example: exclude. One of: `include`, `exclude`.
- `ip` (`string`, optional): Only mail from this IP. Example: 192.0.2.10.
- `limit` (`integer`, optional): Results per page (default 100). Example: 100.
- `mailorigin` (`string`, optional): Only mail from this origin (sending service domain). Example: gmail.com.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `region` (`string`, optional): Only mail from this region or state. Example: California.
- `spfdomain` (`string`, optional): Only mail with this SPF domain. Example: mail.example.com.
- `spfresult` (`string`, optional): Only mail with this SPF result: none, pass, fail, softfail, temperror or permerror. Example: fail. One of: `none`, `pass`, `fail`, `softfail`, `temperror`, `permerror`.
- `startdate` (`string`, optional): Start of the date range, YYYY-MM-DD (a time can follow, YYYY-MM-DD HH:MM:SS, UTC). Defaults to 30 days ago. Example: 2026-10-01.

Example input: `{"domain":"<domain>"}`

### `everest_dmarc_domain_get`

Get DMARC Domain Overview · Read-only

Get a DMARC-monitored domain's overview for a date range.
Returns the domain's DMARC, SPF and DKIM records and policy, total volume, and compliant, non-compliant and unauthenticated shares.
Use everest_dmarc_domain_get for one domain's health. Use everest_dmarc_domain_mail_origins_list to see who sends as the domain.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): The DMARC-monitored domain, without a scheme. Example: example.com.
- `enddate` (`string`, optional): End of the date range, YYYY-MM-DD (or YYYY-MM-DD HH:MM:SS, UTC). Defaults to today. Example: 2026-10-31.
- `startdate` (`string`, optional): Start of the date range, YYYY-MM-DD (a time can follow, YYYY-MM-DD HH:MM:SS, UTC). Defaults to 30 days ago. Example: 2026-10-01.

Example input: `{"domain":"<domain>"}`

### `everest_dmarc_domain_ips_list`

List DMARC IP Addresses · Read-only

List DMARC data for a domain: each sending IP with volume, reverse DNS and DMARC, SPF and DKIM results.
Returns each sending IP with volume, reverse DNS and DMARC, SPF and DKIM results for the date range, paginated.
Use everest_dmarc_domain_ips_list to find the IPs sending as the domain. Use everest_dmarc_domain_get for the domain's overview.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): The DMARC-monitored domain, without a scheme. Example: example.com.
- `classification` (`array`, optional): Only mail with these DMARC classifications: compliant, non-compliant, unauthenticated. Example: ["non-compliant", "unauthenticated"].
- `dkimdomain` (`string`, optional): Only mail with this DKIM domain. Example: mail.example.com.
- `dkimresult` (`string`, optional): Only mail with this DKIM result: none, pass, fail, softfail, temperror or permerror. Example: fail. One of: `none`, `pass`, `fail`, `softfail`, `temperror`, `permerror`.
- `enddate` (`string`, optional): End of the date range, YYYY-MM-DD (or YYYY-MM-DD HH:MM:SS, UTC). Defaults to today. Example: 2026-10-31.
- `forwarded` (`string`, optional): include or exclude forwarded mail. Forwarded mail with a valid ARC chain (arc=pass) had SPF or DKIM validated before forwarding. Example: exclude. One of: `include`, `exclude`.
- `ip` (`string`, optional): Only mail from this IP. Example: 192.0.2.10.
- `limit` (`integer`, optional): Results per page (default 100). Example: 100.
- `mailorigin` (`string`, optional): Only mail from this origin (sending service domain). Example: gmail.com.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `spfdomain` (`string`, optional): Only mail with this SPF domain. Example: mail.example.com.
- `spfresult` (`string`, optional): Only mail with this SPF result: none, pass, fail, softfail, temperror or permerror. Example: fail. One of: `none`, `pass`, `fail`, `softfail`, `temperror`, `permerror`.
- `startdate` (`string`, optional): Start of the date range, YYYY-MM-DD (a time can follow, YYYY-MM-DD HH:MM:SS, UTC). Defaults to 30 days ago. Example: 2026-10-01.

Example input: `{"domain":"<domain>"}`

### `everest_dmarc_domain_mailorigins_list`

List DMARC Mail Origins · Read-only

List DMARC data for a domain: each sending source (mail origin) with volume and DMARC, SPF and DKIM results.
Returns each sending source (mail origin) with volume and DMARC, SPF and DKIM results for the date range, paginated.
Use everest_dmarc_domain_mailorigins_list to find services sending as the domain, authorized or not. Use everest_dmarc_domain_get for the domain's overview.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): The DMARC-monitored domain, without a scheme. Example: example.com.
- `classification` (`array`, optional): Only mail with these DMARC classifications: compliant, non-compliant, unauthenticated. Example: ["non-compliant", "unauthenticated"].
- `dkimdomain` (`string`, optional): Only mail with this DKIM domain. Example: mail.example.com.
- `dkimresult` (`string`, optional): Only mail with this DKIM result: none, pass, fail, softfail, temperror or permerror. Example: fail. One of: `none`, `pass`, `fail`, `softfail`, `temperror`, `permerror`.
- `enddate` (`string`, optional): End of the date range, YYYY-MM-DD (or YYYY-MM-DD HH:MM:SS, UTC). Defaults to today. Example: 2026-10-31.
- `forwarded` (`string`, optional): include or exclude forwarded mail. Forwarded mail with a valid ARC chain (arc=pass) had SPF or DKIM validated before forwarding. Example: exclude. One of: `include`, `exclude`.
- `ip` (`string`, optional): Only mail from this IP. Example: 192.0.2.10.
- `limit` (`integer`, optional): Results per page (default 100). Example: 100.
- `mailorigin` (`string`, optional): Only mail from this origin (sending service domain). Example: gmail.com.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `spfdomain` (`string`, optional): Only mail with this SPF domain. Example: mail.example.com.
- `spfresult` (`string`, optional): Only mail with this SPF result: none, pass, fail, softfail, temperror or permerror. Example: fail. One of: `none`, `pass`, `fail`, `softfail`, `temperror`, `permerror`.
- `startdate` (`string`, optional): Start of the date range, YYYY-MM-DD (a time can follow, YYYY-MM-DD HH:MM:SS, UTC). Defaults to 30 days ago. Example: 2026-10-01.

Example input: `{"domain":"<domain>"}`

### `everest_dmarc_domain_reports_list`

List DMARC Detailed DMARC Reports · Read-only

List DMARC data for a domain: the individual DMARC aggregate report rows (reporter, source IP, counts, SPF and DKIM results).
Returns the individual DMARC aggregate report rows (reporter, source IP, counts, SPF and DKIM results) for the date range, paginated.
Use everest_dmarc_domain_reports_list for row-level DMARC data; keep limit small, since domains can have millions of rows. Use everest_dmarc_domain_get for the domain's overview.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): The DMARC-monitored domain, without a scheme. Example: example.com.
- `city` (`string`, optional): Only mail from this city. Example: San Francisco.
- `classification` (`array`, optional): Only mail with these DMARC classifications: compliant, non-compliant, unauthenticated. Example: ["non-compliant", "unauthenticated"].
- `country` (`string`, optional): Only mail from this country (code or name). Example: US.
- `dkimdomain` (`string`, optional): Only mail with this DKIM domain. Example: mail.example.com.
- `dkimresult` (`string`, optional): Only mail with this DKIM result: none, pass, fail, softfail, temperror or permerror. Example: fail. One of: `none`, `pass`, `fail`, `softfail`, `temperror`, `permerror`.
- `enddate` (`string`, optional): End of the date range, YYYY-MM-DD (or YYYY-MM-DD HH:MM:SS, UTC). Defaults to today. Example: 2026-10-31.
- `forwarded` (`string`, optional): include or exclude forwarded mail. Forwarded mail with a valid ARC chain (arc=pass) had SPF or DKIM validated before forwarding. Example: exclude. One of: `include`, `exclude`.
- `ip` (`string`, optional): Only mail from this IP. Example: 192.0.2.10.
- `limit` (`integer`, optional): Results per page (default 100). Example: 100.
- `mailorigin` (`string`, optional): Only mail from this origin (sending service domain). Example: gmail.com.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `region` (`string`, optional): Only mail from this region or state. Example: California.
- `spfdomain` (`string`, optional): Only mail with this SPF domain. Example: mail.example.com.
- `spfresult` (`string`, optional): Only mail with this SPF result: none, pass, fail, softfail, temperror or permerror. Example: fail. One of: `none`, `pass`, `fail`, `softfail`, `temperror`, `permerror`.
- `startdate` (`string`, optional): Start of the date range, YYYY-MM-DD (a time can follow, YYYY-MM-DD HH:MM:SS, UTC). Defaults to 30 days ago. Example: 2026-10-01.

Example input: `{"domain":"<domain>"}`

### `everest_dmarc_domain_spfdomains_list`

List DMARC SPF Domains · Read-only

List DMARC data for a domain: each SPF (envelope) domain seen with volume and SPF results.
Returns each SPF (envelope) domain seen with volume and SPF results for the date range, paginated.
Use everest_dmarc_domain_spfdomains_list to check which envelope domains align with the domain. Use everest_dmarc_domain_get for the domain's overview.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): The DMARC-monitored domain, without a scheme. Example: example.com.
- `classification` (`array`, optional): Only mail with these DMARC classifications: compliant, non-compliant, unauthenticated. Example: ["non-compliant", "unauthenticated"].
- `dkimdomain` (`string`, optional): Only mail with this DKIM domain. Example: mail.example.com.
- `dkimresult` (`string`, optional): Only mail with this DKIM result: none, pass, fail, softfail, temperror or permerror. Example: fail. One of: `none`, `pass`, `fail`, `softfail`, `temperror`, `permerror`.
- `enddate` (`string`, optional): End of the date range, YYYY-MM-DD (or YYYY-MM-DD HH:MM:SS, UTC). Defaults to today. Example: 2026-10-31.
- `forwarded` (`string`, optional): include or exclude forwarded mail. Forwarded mail with a valid ARC chain (arc=pass) had SPF or DKIM validated before forwarding. Example: exclude. One of: `include`, `exclude`.
- `ip` (`string`, optional): Only mail from this IP. Example: 192.0.2.10.
- `limit` (`integer`, optional): Results per page (default 100). Example: 100.
- `mailorigin` (`string`, optional): Only mail from this origin (sending service domain). Example: gmail.com.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `spfdomain` (`string`, optional): Only mail with this SPF domain. Example: mail.example.com.
- `spfresult` (`string`, optional): Only mail with this SPF result: none, pass, fail, softfail, temperror or permerror. Example: fail. One of: `none`, `pass`, `fail`, `softfail`, `temperror`, `permerror`.
- `startdate` (`string`, optional): Start of the date range, YYYY-MM-DD (a time can follow, YYYY-MM-DD HH:MM:SS, UTC). Defaults to 30 days ago. Example: 2026-10-01.

Example input: `{"domain":"<domain>"}`

### `everest_dmarc_domain_spfresults_list`

List DMARC SPF Authentication Issues · Read-only

List DMARC data for a domain: SPF failures grouped by result and source.
Returns SPF failures grouped by result and source for the date range, paginated.
Use everest_dmarc_domain_spfresults_list to find SPF problems. Use everest_dmarc_domain_get for the domain's overview.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): The DMARC-monitored domain, without a scheme. Example: example.com.
- `classification` (`array`, optional): Only mail with these DMARC classifications: compliant, non-compliant, unauthenticated. Example: ["non-compliant", "unauthenticated"].
- `dkimdomain` (`string`, optional): Only mail with this DKIM domain. Example: mail.example.com.
- `dkimresult` (`string`, optional): Only mail with this DKIM result: none, pass, fail, softfail, temperror or permerror. Example: fail. One of: `none`, `pass`, `fail`, `softfail`, `temperror`, `permerror`.
- `enddate` (`string`, optional): End of the date range, YYYY-MM-DD (or YYYY-MM-DD HH:MM:SS, UTC). Defaults to today. Example: 2026-10-31.
- `forwarded` (`string`, optional): include or exclude forwarded mail. Forwarded mail with a valid ARC chain (arc=pass) had SPF or DKIM validated before forwarding. Example: exclude. One of: `include`, `exclude`.
- `ip` (`string`, optional): Only mail from this IP. Example: 192.0.2.10.
- `limit` (`integer`, optional): Results per page (default 100). Example: 100.
- `mailorigin` (`string`, optional): Only mail from this origin (sending service domain). Example: gmail.com.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `spfdomain` (`string`, optional): Only mail with this SPF domain. Example: mail.example.com.
- `spfresult` (`string`, optional): Only mail with this SPF result: none, pass, fail, softfail, temperror or permerror. Example: fail. One of: `none`, `pass`, `fail`, `softfail`, `temperror`, `permerror`.
- `startdate` (`string`, optional): Start of the date range, YYYY-MM-DD (a time can follow, YYYY-MM-DD HH:MM:SS, UTC). Defaults to 30 days ago. Example: 2026-10-01.

Example input: `{"domain":"<domain>"}`

### `everest_dmarc_domains_list`

List DMARC Domains · Read-only

List the domains monitored for DMARC with their policies and authentication summary.
Returns each domain with its DMARC policy, message volume and compliant, non-compliant and unauthenticated counts for the date range.
Use everest_dmarc_domains_list for an overview. Use everest_dmarc_domain_get for one domain.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `classification` (`array`, optional): Only mail with these DMARC classifications: compliant, non-compliant, unauthenticated. Example: ["non-compliant", "unauthenticated"].
- `dkimdomain` (`string`, optional): Only mail with this DKIM domain. Example: mail.example.com.
- `dkimresult` (`string`, optional): Only mail with this DKIM result: none, pass, fail, softfail, temperror or permerror. Example: fail. One of: `none`, `pass`, `fail`, `softfail`, `temperror`, `permerror`.
- `enddate` (`string`, optional): End of the date range, YYYY-MM-DD (or YYYY-MM-DD HH:MM:SS, UTC). Defaults to today. Example: 2026-10-31.
- `forwarded` (`string`, optional): include or exclude forwarded mail. Forwarded mail with a valid ARC chain (arc=pass) had SPF or DKIM validated before forwarding. Example: exclude. One of: `include`, `exclude`.
- `ip` (`string`, optional): Only mail from this IP. Example: 192.0.2.10.
- `limit` (`integer`, optional): Results per page (default 100). Example: 100.
- `mailorigin` (`string`, optional): Only mail from this origin (sending service domain). Example: gmail.com.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `spfdomain` (`string`, optional): Only mail with this SPF domain. Example: mail.example.com.
- `spfresult` (`string`, optional): Only mail with this SPF result: none, pass, fail, softfail, temperror or permerror. Example: fail. One of: `none`, `pass`, `fail`, `softfail`, `temperror`, `permerror`.
- `startdate` (`string`, optional): Start of the date range, YYYY-MM-DD (a time can follow, YYYY-MM-DD HH:MM:SS, UTC). Defaults to 30 days ago. Example: 2026-10-01.

Example input: `{}`

### `everest_gpt_domain_authentication_get`

Get Google Postmaster Authentication · Read-only

Get Google Postmaster Tools authentication data for a domain.
Returns daily SPF, DKIM and DMARC pass rates Gmail saw.
Use everest_gpt_domain_authentication_get for Gmail-specific deliverability signals. Use everest_gpt_domains_list to find connected domains.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): The Google Postmaster Tools verified domain, without a scheme. Example: example.com.

Example input: `{"domain":"<domain>"}`

### `everest_gpt_domain_domainreputation_get`

Get Google Postmaster Domain Reputation · Read-only

Get Google Postmaster Tools domain reputation data for a domain.
Returns Gmail's daily domain reputation (bad, low, medium, high) with totals for the range.
Use everest_gpt_domain_domainreputation_get for Gmail-specific deliverability signals. Use everest_gpt_domains_list to find connected domains.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): The Google Postmaster Tools verified domain, without a scheme. Example: example.com.

Example input: `{"domain":"<domain>"}`

### `everest_gpt_domain_errors_get`

Get Google Postmaster Delivery Errors · Read-only

Get Google Postmaster Tools delivery errors data for a domain.
Returns rejected and temp-failed Gmail traffic against all authenticated traffic, by day and error type.
Use everest_gpt_domain_errors_get for Gmail-specific deliverability signals. Use everest_gpt_domains_list to find connected domains.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): The Google Postmaster Tools verified domain, without a scheme. Example: example.com.

Example input: `{"domain":"<domain>"}`

### `everest_gpt_domain_feedback_get`

Get Google Postmaster Feedback Loop · Read-only

Get Google Postmaster Tools feedback loop data for a domain.
Returns Gmail feedback loop spam rates by identifier.
Use everest_gpt_domain_feedback_get for Gmail-specific deliverability signals. Use everest_gpt_domains_list to find connected domains.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): The Google Postmaster Tools verified domain, without a scheme. Example: example.com.

Example input: `{"domain":"<domain>"}`

### `everest_gpt_domain_get`

Get Google Postmaster Overview · Read-only

Get Google Postmaster Tools overview data for a domain.
Returns the domain's Gmail domain and IP reputation, spam rate, delivery errors, feedback loop and authentication data.
Use everest_gpt_domain_get for Gmail-specific deliverability signals. Use everest_gpt_domains_list to find connected domains.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): The Google Postmaster Tools verified domain, without a scheme. Example: example.com.

Example input: `{"domain":"<domain>"}`

### `everest_gpt_domain_ipreputation_get`

Get Google Postmaster IP Reputation · Read-only

Get Google Postmaster Tools ip reputation data for a domain.
Returns Gmail's reputation for the domain's sending IPs, by day and reputation level.
Use everest_gpt_domain_ipreputation_get for Gmail-specific deliverability signals. Use everest_gpt_domains_list to find connected domains.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): The Google Postmaster Tools verified domain, without a scheme. Example: example.com.
- `offset` (`integer`, optional): Record offset for results over 1,000 rows, as given in the response's endpoints object. Example: 1000.

Example input: `{"domain":"<domain>"}`

### `everest_gpt_domain_spam_get`

Get Google Postmaster Spam Rate · Read-only

Get Google Postmaster Tools spam rate data for a domain.
Returns the daily user-reported spam rate for DKIM-authenticated mail.
Use everest_gpt_domain_spam_get for Gmail-specific deliverability signals. Use everest_gpt_domains_list to find connected domains.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): The Google Postmaster Tools verified domain, without a scheme. Example: example.com.

Example input: `{"domain":"<domain>"}`

### `everest_gpt_domains_list`

List Google Postmaster Domains · Read-only

List the Google Postmaster Tools domains connected to Everest, with a summary of each.
Returns each verified domain with its latest domain and IP reputation, spam rate, delivery errors and authentication rates, plus endpoints for detail.
Use everest_gpt_domains_list for a Gmail overview. Needs a Google Postmaster Tools integration with verified domains in Everest.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `everest_inbox_placement_by_b2b_get`

Get Inbox Placement by B2B · Read-only

Get aggregate inbox placement across the account's inbox tests, grouped by business (B2B) mailbox provider.
Returns one row per business (B2B) mailbox provider with inbox, spam and missing counts and percentages.
Use everest_inbox_placement_by_b2b_get for trends across tests. Use everest_inbox_test_get for a single test.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `everest_inbox_placement_by_b2c_get`

Get Inbox Placement by B2C · Read-only

Get aggregate inbox placement across the account's inbox tests, grouped by consumer (B2C) mailbox provider.
Returns one row per consumer (B2C) mailbox provider with inbox, spam and missing counts and percentages.
Use everest_inbox_placement_by_b2c_get for trends across tests. Use everest_inbox_test_get for a single test.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `everest_inbox_placement_by_fromaddress_get`

Get Inbox Placement by From Address · Read-only

Get aggregate inbox placement across the account's inbox tests, grouped by From address.
Returns one row per From address with inbox, spam and missing counts and percentages.
Use everest_inbox_placement_by_fromaddress_get for trends across tests. Use everest_inbox_test_get for a single test.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `everest_inbox_placement_by_fromdomain_get`

Get Inbox Placement by From Domain · Read-only

Get aggregate inbox placement across the account's inbox tests, grouped by From domain.
Returns one row per From domain with inbox, spam and missing counts and percentages.
Use everest_inbox_placement_by_fromdomain_get for trends across tests. Use everest_inbox_test_get for a single test.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `everest_inbox_placement_by_region_get`

Get Inbox Placement by Region · Read-only

Get aggregate inbox placement across the account's inbox tests, grouped by seed region.
Returns one row per seed region with inbox, spam and missing counts and percentages.
Use everest_inbox_placement_by_region_get for trends across tests. Use everest_inbox_test_get for a single test.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `everest_inbox_test_get`

Get Inbox Test · Read-only

Get one inbox placement test's results.
Returns the test's subject, sender, IPs, authentication results, and inbox, spam and missing placement overall and by region.
Use everest_inbox_test_get for a test's summary. Use everest_inbox_test_providers_list for per-provider placement.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `test_id` (`string`, required): ID of the inbox test, from everest_inbox_tests_list. Example: 3542086.

Example input: `{"test_id":"<test_id>"}`

### `everest_inbox_test_headers_get`

Get Inbox Test Mailbox Headers · Read-only

Get the headers one seed mailbox received in an inbox placement test.
Returns the test ID, header ID and the raw received headers, including authentication results and filter verdicts.
Use everest_inbox_test_headers_get to debug why a provider filtered the message. Get the mailbox ID from everest_inbox_test_provider_get.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `mailbox_id` (`string`, required): ID of the seed mailbox, from everest_inbox_test_provider_get. Example: 2346219767.
- `provider_id` (`string`, required): ID of the mailbox provider, from everest_inbox_test_providers_list or everest_seed_regions_list. Example: 34.
- `test_id` (`string`, required): ID of the inbox test, from everest_inbox_tests_list. Example: 3542086.

Example input: `{"mailbox_id":"<mailbox_id>","provider_id":"<provider_id>","test_id":"<test_id>"}`

### `everest_inbox_test_message_get`

Get Inbox Test Message · Read-only

Get the message that was tested in an inbox placement test.
Returns the full raw message, its HTML and text versions, and its headers.
Use everest_inbox_test_message_get to review the content behind a test's results. Use everest_inbox_test_headers_get for one seed mailbox's received headers.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `test_id` (`string`, required): ID of the inbox test, from everest_inbox_tests_list. Example: 3542086.

Example input: `{"test_id":"<test_id>"}`

### `everest_inbox_test_provider_get`

Get Inbox Test Provider Result · Read-only

Get an inbox placement test's results for one mailbox provider.
Returns the provider's placement figures and each seed mailbox with its folder (inbox, spam or missing) and mailbox ID.
Use everest_inbox_test_provider_get to drill into one provider. Use everest_inbox_test_headers_get with a mailbox ID for its received headers.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `provider_id` (`string`, required): ID of the mailbox provider, from everest_inbox_test_providers_list or everest_seed_regions_list. Example: 34.
- `test_id` (`string`, required): ID of the inbox test, from everest_inbox_tests_list. Example: 3542086.

Example input: `{"provider_id":"<provider_id>","test_id":"<test_id>"}`

### `everest_inbox_test_providers_list`

List Inbox Test Provider Results · Read-only

Get an inbox placement test's results for every mailbox provider.
Returns each provider (Gmail, Yahoo, Outlook and others) with its inbox, spam and missing counts and percentages and its seed mailboxes.
Use everest_inbox_test_providers_list to see where placement failed. Use everest_inbox_test_provider_get for one provider's mailboxes.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `test_id` (`string`, required): ID of the inbox test, from everest_inbox_tests_list. Example: 3542086.

Example input: `{"test_id":"<test_id>"}`

### `everest_inbox_tests_list`

List Inbox Tests · Read-only

List the account's inbox placement tests, newest first.
Returns tests with id, subject, from address, sending IP, date and inbox, spam and missing percentages.
Use everest_inbox_tests_list to find tests by date, IP, SPF or DKIM domain, or region. Use everest_inbox_test_get for one test's detail.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `dkimdomain` (`string`, optional): Only tests signed with this DKIM domain. Example: example.com.
- `enddate` (`string`, optional): End of the date range, YYYY-MM-DD (or YYYY-MM-DD HH:MM:SS, UTC). Defaults to today. Example: 2026-10-31.
- `ip` (`string`, optional): Only tests sent from this IP. Example: 192.0.2.10.
- `limit` (`integer`, optional): Results per page (default 100). Example: 100.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `region_id` (`integer`, optional): Only results for this seed region, from everest_seed_regions_list. Example: 1.
- `spfdomain` (`string`, optional): Only tests with this SPF (envelope) domain. Example: mail.example.com.
- `startdate` (`string`, optional): Start of the date range, YYYY-MM-DD (a time can follow, YYYY-MM-DD HH:MM:SS, UTC). Defaults to 30 days ago. Example: 2026-10-01.

Example input: `{}`

### `everest_mailbox_provider_health_get`

Get Mailbox Provider Health · Read-only

Get daily inbox, spam and missing averages for each mailbox provider across the Everest community, as a benchmark.
Returns totals for the date range and the same figures per day, for every region and provider.
Use everest_mailbox_provider_health_get to tell whether a placement drop is yours or the provider's. Compare with everest_inbox_placement_by_b2c_get.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `enddate` (`string`, optional): End of the date range, YYYY-MM-DD (or YYYY-MM-DD HH:MM:SS, UTC). Defaults to today. Example: 2026-10-31.
- `startdate` (`string`, optional): Start of the date range, YYYY-MM-DD (a time can follow, YYYY-MM-DD HH:MM:SS, UTC). Defaults to 30 days ago. Example: 2026-10-01.

Example input: `{}`

### `everest_reputation_items_list`

List All Monitored Items · Read-only

List every IP, range and domain monitored across all reputation profiles.
Returns each item with its value, type, description and profile.
Use everest_reputation_items_list for the full monitored inventory. Use everest_reputation_profile_items_list for one profile.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `type` (`string`, optional): Kind of monitored item: ip, cidr, ip_range, domain_name or shared_domain. Example: ip. One of: `ip`, `cidr`, `ip_range`, `domain_name`, `shared_domain`.

Example input: `{}`

### `everest_reputation_profile_get`

Get Reputation Profile · Read-only

Get one reputation profile with its blocklist hits and issue metrics.
Returns the profile's name, tracked blocklists, enabled state, blocklist hits and issue counts.
Use everest_reputation_profile_get for one profile. Use everest_reputation_profile_items_list for the IPs and domains it tracks.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `profile_id` (`string`, required): ID of the reputation profile, from everest_reputation_profiles_list. Example: 1.

Example input: `{"profile_id":"<profile_id>"}`

### `everest_reputation_profile_items_list`

List Reputation Profile Items · Read-only

List the IPs, ranges and domains a reputation profile monitors.
Returns each item with its ID, value, type and description.
Use everest_reputation_profile_items_list to see or find an item ID before everest_reputation_profile_item_delete. Use everest_reputation_items_list for items across all profiles.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `profile_id` (`string`, required): ID of the reputation profile, from everest_reputation_profiles_list. Example: 1.
- `type` (`string`, optional): Kind of monitored item: ip, cidr, ip_range, domain_name or shared_domain. Example: ip. One of: `ip`, `cidr`, `ip_range`, `domain_name`, `shared_domain`.

Example input: `{"profile_id":"<profile_id>"}`

### `everest_reputation_profile_rdns_issues_list`

List Reputation Profile rDNS Issues · Read-only

List reverse DNS (rDNS) problems for the IPs in a reputation profile.
Returns each IP with its rDNS issue, such as a missing PTR record or a forward lookup that does not match.
Use everest_reputation_profile_rdns_issues_list to find sending IPs whose rDNS hurts deliverability.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `profile_id` (`string`, required): ID of the reputation profile, from everest_reputation_profiles_list. Example: 1.

Example input: `{"profile_id":"<profile_id>"}`

### `everest_reputation_profiles_list`

List Reputation Profiles · Read-only

List the account's reputation profiles (groups of monitored IPs and domains).
Returns each profile with its ID, name, tracked blocklists, current blocklist hits and issue metrics.
Use everest_reputation_profiles_list for an overview. Use everest_reputation_profile_get for one profile.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `everest_seed_list_get`

Get Seed List · Read-only

Get the account's inbox placement seed list.
Returns the seed email addresses to include in a campaign, with their regions and mailbox providers.
Use everest_seed_list_get to get the addresses to add to a send for an inbox test. Use everest_seed_regions_list to see which regions can be added.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `everest_seed_regions_list`

List Seed Regions and Providers · Read-only

List the regions that can be added to the seed list, with the mailbox providers in each.
Returns regions with id and name, each with its providers (id and name, for example Gmail, AOL, Apple).
Use everest_seed_regions_list to pick region IDs for everest_seed_list_update, and provider IDs for the inbox test provider tools.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `everest_sender_score_get`

Get Sender Score · Read-only

Get Validity Sender Score detail for an IP address.
Returns the IP's Sender Score (0-100, higher is better) with its history and the factors behind it.
Use everest_sender_score_get to check a sending IP's reputation. Use everest_blocklist_listings_list for blocklist status.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `ip` (`string`, required): The IPv4 address to look up. Example: 192.0.2.10.

Example input: `{"ip":"<ip>"}`

### `everest_spam_trap_events_list`

List Spam Trap Events · Read-only

List individual spam trap hits with message detail.
Returns each hit with date, trap type, sending IP, From address and domain, display name, subject and profile.
Use everest_spam_trap_events_list to investigate specific hits. Use the everest_spam_traps_by_* tools for grouped counts.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `enddate` (`string`, optional): End of the date range, YYYY-MM-DD (or YYYY-MM-DD HH:MM:SS, UTC). Defaults to today. Example: 2026-10-31.
- `friendlyfrom` (`string`, optional): Only hits with this From display name. Example: Acme Co.
- `fromaddress` (`string`, optional): Only hits from this From address. Example: news@example.com.
- `fromdomain` (`string`, optional): Only hits from this From domain. Example: example.com.
- `ip` (`string`, optional): Only hits from this sending IP. Example: 192.0.2.10.
- `limit` (`integer`, optional): Results per page (default 100). Example: 100.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `profile_id` (`integer`, optional): Only hits for IPs in this reputation profile, from everest_reputation_profiles_list. Example: 1.
- `startdate` (`string`, optional): Start of the date range, YYYY-MM-DD (a time can follow, YYYY-MM-DD HH:MM:SS, UTC). Defaults to 30 days ago. Example: 2026-10-01.
- `subject` (`string`, optional): Only hits on messages with this subject. Example: Spring sale.
- `traptype` (`string`, optional): Only hits on this trap type: pristine, typo or recycled. Example: pristine. One of: `pristine`, `typo`, `recycled`.

Example input: `{}`

### `everest_spam_traps_by_day_get`

Get Spam Trap Hits by Day · Read-only

Get spam trap hits in your mail stream, grouped by day.
Returns one row per day with trap hit counts by type (pristine, typo, recycled).
Use everest_spam_traps_by_day_get to find which day hits traps. Use everest_spam_trap_events_list for the individual hits.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `enddate` (`string`, optional): End of the date range, YYYY-MM-DD (or YYYY-MM-DD HH:MM:SS, UTC). Defaults to today. Example: 2026-10-31.
- `friendlyfrom` (`string`, optional): Only hits with this From display name. Example: Acme Co.
- `fromaddress` (`string`, optional): Only hits from this From address. Example: news@example.com.
- `fromdomain` (`string`, optional): Only hits from this From domain. Example: example.com.
- `ip` (`string`, optional): Only hits from this sending IP. Example: 192.0.2.10.
- `limit` (`integer`, optional): Results per page (default 100). Example: 100.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `profile_id` (`integer`, optional): Only hits for IPs in this reputation profile, from everest_reputation_profiles_list. Example: 1.
- `startdate` (`string`, optional): Start of the date range, YYYY-MM-DD (a time can follow, YYYY-MM-DD HH:MM:SS, UTC). Defaults to 30 days ago. Example: 2026-10-01.
- `subject` (`string`, optional): Only hits on messages with this subject. Example: Spring sale.
- `traptype` (`string`, optional): Only hits on this trap type: pristine, typo or recycled. Example: pristine. One of: `pristine`, `typo`, `recycled`.

Example input: `{}`

### `everest_spam_traps_by_friendlyfrom_get`

Get Spam Trap Hits by Friendly From · Read-only

Get spam trap hits in your mail stream, grouped by friendly from.
Returns one row per friendly from with trap hit counts by type (pristine, typo, recycled).
Use everest_spam_traps_by_friendlyfrom_get to find which friendly from hits traps. Use everest_spam_trap_events_list for the individual hits.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `enddate` (`string`, optional): End of the date range, YYYY-MM-DD (or YYYY-MM-DD HH:MM:SS, UTC). Defaults to today. Example: 2026-10-31.
- `friendlyfrom` (`string`, optional): Only hits with this From display name. Example: Acme Co.
- `fromaddress` (`string`, optional): Only hits from this From address. Example: news@example.com.
- `fromdomain` (`string`, optional): Only hits from this From domain. Example: example.com.
- `ip` (`string`, optional): Only hits from this sending IP. Example: 192.0.2.10.
- `limit` (`integer`, optional): Results per page (default 100). Example: 100.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `profile_id` (`integer`, optional): Only hits for IPs in this reputation profile, from everest_reputation_profiles_list. Example: 1.
- `startdate` (`string`, optional): Start of the date range, YYYY-MM-DD (a time can follow, YYYY-MM-DD HH:MM:SS, UTC). Defaults to 30 days ago. Example: 2026-10-01.
- `subject` (`string`, optional): Only hits on messages with this subject. Example: Spring sale.
- `traptype` (`string`, optional): Only hits on this trap type: pristine, typo or recycled. Example: pristine. One of: `pristine`, `typo`, `recycled`.

Example input: `{}`

### `everest_spam_traps_by_fromaddress_get`

Get Spam Trap Hits by From Address · Read-only

Get spam trap hits in your mail stream, grouped by from address.
Returns one row per from address with trap hit counts by type (pristine, typo, recycled).
Use everest_spam_traps_by_fromaddress_get to find which from address hits traps. Use everest_spam_trap_events_list for the individual hits.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `enddate` (`string`, optional): End of the date range, YYYY-MM-DD (or YYYY-MM-DD HH:MM:SS, UTC). Defaults to today. Example: 2026-10-31.
- `friendlyfrom` (`string`, optional): Only hits with this From display name. Example: Acme Co.
- `fromaddress` (`string`, optional): Only hits from this From address. Example: news@example.com.
- `fromdomain` (`string`, optional): Only hits from this From domain. Example: example.com.
- `ip` (`string`, optional): Only hits from this sending IP. Example: 192.0.2.10.
- `limit` (`integer`, optional): Results per page (default 100). Example: 100.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `profile_id` (`integer`, optional): Only hits for IPs in this reputation profile, from everest_reputation_profiles_list. Example: 1.
- `startdate` (`string`, optional): Start of the date range, YYYY-MM-DD (a time can follow, YYYY-MM-DD HH:MM:SS, UTC). Defaults to 30 days ago. Example: 2026-10-01.
- `subject` (`string`, optional): Only hits on messages with this subject. Example: Spring sale.
- `traptype` (`string`, optional): Only hits on this trap type: pristine, typo or recycled. Example: pristine. One of: `pristine`, `typo`, `recycled`.

Example input: `{}`

### `everest_spam_traps_by_fromdomain_get`

Get Spam Trap Hits by From Domain · Read-only

Get spam trap hits in your mail stream, grouped by from domain.
Returns one row per from domain with trap hit counts by type (pristine, typo, recycled).
Use everest_spam_traps_by_fromdomain_get to find which from domain hits traps. Use everest_spam_trap_events_list for the individual hits.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `enddate` (`string`, optional): End of the date range, YYYY-MM-DD (or YYYY-MM-DD HH:MM:SS, UTC). Defaults to today. Example: 2026-10-31.
- `friendlyfrom` (`string`, optional): Only hits with this From display name. Example: Acme Co.
- `fromaddress` (`string`, optional): Only hits from this From address. Example: news@example.com.
- `fromdomain` (`string`, optional): Only hits from this From domain. Example: example.com.
- `ip` (`string`, optional): Only hits from this sending IP. Example: 192.0.2.10.
- `limit` (`integer`, optional): Results per page (default 100). Example: 100.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `profile_id` (`integer`, optional): Only hits for IPs in this reputation profile, from everest_reputation_profiles_list. Example: 1.
- `startdate` (`string`, optional): Start of the date range, YYYY-MM-DD (a time can follow, YYYY-MM-DD HH:MM:SS, UTC). Defaults to 30 days ago. Example: 2026-10-01.
- `subject` (`string`, optional): Only hits on messages with this subject. Example: Spring sale.
- `traptype` (`string`, optional): Only hits on this trap type: pristine, typo or recycled. Example: pristine. One of: `pristine`, `typo`, `recycled`.

Example input: `{}`

### `everest_spam_traps_by_ip_get`

Get Spam Trap Hits by IP · Read-only

Get spam trap hits in your mail stream, grouped by ip.
Returns one row per ip with trap hit counts by type (pristine, typo, recycled).
Use everest_spam_traps_by_ip_get to find which ip hits traps. Use everest_spam_trap_events_list for the individual hits.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `enddate` (`string`, optional): End of the date range, YYYY-MM-DD (or YYYY-MM-DD HH:MM:SS, UTC). Defaults to today. Example: 2026-10-31.
- `friendlyfrom` (`string`, optional): Only hits with this From display name. Example: Acme Co.
- `fromaddress` (`string`, optional): Only hits from this From address. Example: news@example.com.
- `fromdomain` (`string`, optional): Only hits from this From domain. Example: example.com.
- `ip` (`string`, optional): Only hits from this sending IP. Example: 192.0.2.10.
- `limit` (`integer`, optional): Results per page (default 100). Example: 100.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `profile_id` (`integer`, optional): Only hits for IPs in this reputation profile, from everest_reputation_profiles_list. Example: 1.
- `startdate` (`string`, optional): Start of the date range, YYYY-MM-DD (a time can follow, YYYY-MM-DD HH:MM:SS, UTC). Defaults to 30 days ago. Example: 2026-10-01.
- `subject` (`string`, optional): Only hits on messages with this subject. Example: Spring sale.
- `traptype` (`string`, optional): Only hits on this trap type: pristine, typo or recycled. Example: pristine. One of: `pristine`, `typo`, `recycled`.

Example input: `{}`

### `everest_spam_traps_by_profile_get`

Get Spam Trap Hits by Profile · Read-only

Get spam trap hits in your mail stream, grouped by profile.
Returns one row per profile with trap hit counts by type (pristine, typo, recycled).
Use everest_spam_traps_by_profile_get to find which profile hits traps. Use everest_spam_trap_events_list for the individual hits.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `enddate` (`string`, optional): End of the date range, YYYY-MM-DD (or YYYY-MM-DD HH:MM:SS, UTC). Defaults to today. Example: 2026-10-31.
- `friendlyfrom` (`string`, optional): Only hits with this From display name. Example: Acme Co.
- `fromaddress` (`string`, optional): Only hits from this From address. Example: news@example.com.
- `fromdomain` (`string`, optional): Only hits from this From domain. Example: example.com.
- `ip` (`string`, optional): Only hits from this sending IP. Example: 192.0.2.10.
- `limit` (`integer`, optional): Results per page (default 100). Example: 100.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `profile_id` (`integer`, optional): Only hits for IPs in this reputation profile, from everest_reputation_profiles_list. Example: 1.
- `startdate` (`string`, optional): Start of the date range, YYYY-MM-DD (a time can follow, YYYY-MM-DD HH:MM:SS, UTC). Defaults to 30 days ago. Example: 2026-10-01.
- `subject` (`string`, optional): Only hits on messages with this subject. Example: Spring sale.
- `traptype` (`string`, optional): Only hits on this trap type: pristine, typo or recycled. Example: pristine. One of: `pristine`, `typo`, `recycled`.

Example input: `{}`

### `everest_spam_traps_by_subject_get`

Get Spam Trap Hits by Subject · Read-only

Get spam trap hits in your mail stream, grouped by subject.
Returns one row per subject with trap hit counts by type (pristine, typo, recycled).
Use everest_spam_traps_by_subject_get to find which subject hits traps. Use everest_spam_trap_events_list for the individual hits.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `enddate` (`string`, optional): End of the date range, YYYY-MM-DD (or YYYY-MM-DD HH:MM:SS, UTC). Defaults to today. Example: 2026-10-31.
- `friendlyfrom` (`string`, optional): Only hits with this From display name. Example: Acme Co.
- `fromaddress` (`string`, optional): Only hits from this From address. Example: news@example.com.
- `fromdomain` (`string`, optional): Only hits from this From domain. Example: example.com.
- `ip` (`string`, optional): Only hits from this sending IP. Example: 192.0.2.10.
- `limit` (`integer`, optional): Results per page (default 100). Example: 100.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `profile_id` (`integer`, optional): Only hits for IPs in this reputation profile, from everest_reputation_profiles_list. Example: 1.
- `startdate` (`string`, optional): Start of the date range, YYYY-MM-DD (a time can follow, YYYY-MM-DD HH:MM:SS, UTC). Defaults to 30 days ago. Example: 2026-10-01.
- `subject` (`string`, optional): Only hits on messages with this subject. Example: Spring sale.
- `traptype` (`string`, optional): Only hits on this trap type: pristine, typo or recycled. Example: pristine. One of: `pristine`, `typo`, `recycled`.

Example input: `{}`

### `everest_suspicious_events_list`

List Suspicious Message Events · Read-only

List suspicious messages seen in your mail stream.
Returns each event with date, type, sending IP, From address and domain, display name and subject.
Use everest_suspicious_events_list to spot spoofing or unexpected traffic. Use everest_spam_trap_events_list for trap hits.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `enddate` (`string`, optional): End of the date range, YYYY-MM-DD (or YYYY-MM-DD HH:MM:SS, UTC). Defaults to today. Example: 2026-10-31.
- `friendlyfrom` (`string`, optional): Only hits with this From display name. Example: Acme Co.
- `fromaddress` (`string`, optional): Only hits from this From address. Example: news@example.com.
- `fromdomain` (`string`, optional): Only hits from this From domain. Example: example.com.
- `ip` (`string`, optional): Only hits from this sending IP. Example: 192.0.2.10.
- `limit` (`integer`, optional): Results per page (default 100). Example: 100.
- `page` (`integer`, optional): Page number, starting at 1. Example: 1.
- `startdate` (`string`, optional): Start of the date range, YYYY-MM-DD (a time can follow, YYYY-MM-DD HH:MM:SS, UTC). Defaults to 30 days ago. Example: 2026-10-01.
- `subject` (`string`, optional): Only hits on messages with this subject. Example: Spring sale.
- `type` (`string`, optional): Only events of this type. Example: pristine.

Example input: `{}`

### `everest_validation_classifications_list`

List Validation Classifications · Read-only

List every email validation result classification with its meaning.
Returns each category (valid, email_address_invalid, email_domain_invalid, email_account_invalid, accept_all, role_address, disposable, unknown, mailbox_full) with status, name, definition, risk and recommendation (send or suppress).
Use everest_validation_classifications_list to interpret a category returned by everest_email_validate or a list's results.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `everest_validation_list_export_get`

Get Validation List Addresses by Classification · Read-only

Get the email addresses of a completed validation list that fall in one classification.
Returns the addresses with their validation results for that classification.
Use everest_validation_list_export_get to pull, for example, all valid or all disposable addresses after everest_validation_list_get shows status complete.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `classification` (`string`, required): Which addresses to export: all, valid, email_address_invalid, email_domain_invalid, email_account_invalid, accept_all, role_address, disposable, unknown or mailbox_full. Example: valid. One of: `all`, `valid`, `email_address_invalid`, `email_domain_invalid`, `email_account_invalid`, `accept_all`, `role_address`, `disposable`, `unknown`, `mailbox_full`.
- `list_id` (`string`, required): ID of the validation list, from everest_validation_lists_list or everest_validation_list_create. Example: 12345.

Example input: `{"classification":"all","list_id":"<list_id>"}`

### `everest_validation_list_exports_get`

Get Validation List Exports · Read-only

Get the export endpoints of a completed validation list, one per classification.
Returns the list's id, status, expiration and an endpoints object (all, valid, email_address_invalid, accept_all, role_address, disposable, unknown and others).
Use everest_validation_list_exports_get to see which exports exist. Use everest_validation_list_export_get to fetch one classification's addresses.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_id` (`string`, required): ID of the validation list, from everest_validation_lists_list or everest_validation_list_create. Example: 12345.

Example input: `{"list_id":"<list_id>"}`

### `everest_validation_list_get`

Get Validation List · Read-only

Get one validation list's progress and results summary.
Returns status, processed percentage, and the number and percentage of addresses in each classification, plus export endpoints.
Use everest_validation_list_get to poll a list until status is complete. Use everest_validation_list_export_get to fetch the addresses.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_id` (`string`, required): ID of the validation list, from everest_validation_lists_list or everest_validation_list_create. Example: 12345.

Example input: `{"list_id":"<list_id>"}`

### `everest_validation_lists_list`

List Validation Lists · Read-only

List the account's validation lists.
Returns each list with id, description, status (complete when done), processed percentage, totals and percentages per classification, and export endpoints.
Use everest_validation_lists_list to find list IDs and progress. Use everest_validation_list_get for one list.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `everest_dmarc_domain_create`

Add DMARC Domain · Write

Add a domain to DMARC monitoring.
Returns the domain and status success.
Use everest_dmarc_domain_create to start collecting DMARC reports for a domain. Its DMARC record must send aggregate reports (rua) to Everest's address for data to arrive.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `domain` (`string`, required): The sending domain, without a scheme. Example: example.com.

Example input: `{"domain":"<domain>"}`

### `everest_email_validate`

Validate Email Address · Write

Validate one email address in real time; it uses a validation credit.
Returns category, status (valid or invalid), name, definition, risk, recommendation (send or suppress), the address, and diagnostics (role_address, disposable, typo and typo_suggestion).
Use everest_email_validate for one address. Use everest_validation_list_create for many addresses at once.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `email` (`string`, required): The email address to validate. Example: jane@example.com.

Example input: `{"email":"<email>"}`

### `everest_reputation_profile_create`

Create Reputation Profile · Write

Create a reputation profile that monitors IPs and domains against blocklists.
Returns the new profile with its ID.
Use everest_reputation_profile_create, then add IPs or domains with everest_reputation_profile_item_add. Give type or blocklists.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): Profile name. Example: Marketing IPs.
- `blocklists` (`string`, optional): Comma-separated blocklist IDs to track, from everest_blocklists_list, or all. Required when type is not set. Example: 1,2,3.
- `type` (`string`, optional): Track every blocklist of this type: all, ip or domain. When set, blocklists is ignored. Example: all. One of: `all`, `ip`, `domain`.

Example input: `{"name":"<name>"}`

### `everest_reputation_profile_item_add`

Add Reputation Profile Item · Write

Add an IP, IP range, CIDR block or domain to a reputation profile for blocklist monitoring.
Returns the status and profile ID.
Use everest_reputation_profile_item_add to start monitoring a sending IP or domain. Use everest_reputation_profile_item_delete to stop.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `item` (`string`, required): The value to monitor: an IP (192.0.2.10), IP range (192.0.2.1-10), CIDR (192.0.2.0/24) or domain (example.com). Example: 192.0.2.10.
- `profile_id` (`string`, required): ID of the reputation profile, from everest_reputation_profiles_list. Example: 1.
- `type` (`string`, required): Kind of monitored item: ip, cidr, ip_range, domain_name or shared_domain. Example: ip. One of: `ip`, `cidr`, `ip_range`, `domain_name`, `shared_domain`.
- `description` (`string`, optional): Optional description of the item. Example: Primary marketing IP.
- `esps` (`string`, optional): Comma-separated ESP IDs. Required when type is shared_domain. Example: 4,7.

Example input: `{"item":"<item>","profile_id":"<profile_id>","type":"ip"}`

### `everest_reputation_profile_update`

Update Reputation Profile · Write

Change a reputation profile's name, tracked blocklists or monitoring state.
Returns the updated profile.
Use everest_reputation_profile_update to switch blocklists or pause monitoring. Give type or blocklists.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `name` (`string`, required): The profile's name. Example: Marketing IPs.
- `profile_id` (`string`, required): ID of the reputation profile, from everest_reputation_profiles_list. Example: 1.
- `blocklists` (`string`, optional): Comma-separated blocklist IDs to track, from everest_blocklists_list, or all. Required when type is not set. Example: 1,2,3.
- `enabled` (`integer`, optional): 1 to monitor this profile, 0 to pause it. Example: 1. One of: `0`, `1`.
- `type` (`string`, optional): Track every blocklist of this type: all, ip or domain. When set, blocklists is ignored. Example: all. One of: `all`, `ip`, `domain`.

Example input: `{"name":"<name>","profile_id":"<profile_id>"}`

### `everest_seed_list_update`

Update Seed List Regions · Write

Set which regions the account's seed list covers.
Returns the updated seed list.
Use everest_seed_list_update to change regions. Get valid region IDs from everest_seed_regions_list; regions left out are removed.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `regions` (`string`, required): Comma-separated region IDs the seed list should cover, from everest_seed_regions_list. Example: 1,2,3.

Example input: `{"regions":"<regions>"}`

### `everest_validation_list_create`

Create Validation List · Write

Submit a batch of email addresses for validation as a new list; each address uses a validation credit.
Returns the new list with its id, status and progress. Validation runs in the background.
Use everest_validation_list_create for many addresses. Poll everest_validation_list_get until status is complete, then read addresses with everest_validation_list_export_get.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `description` (`string`, required): Name or description of the list. Example: Checkout customers.
- `emails` (`string`, required): The email addresses as one string, separated by the delimiter (comma by default). Example: a@example.com,b@example.com.
- `delimiter` (`string`, optional): Character between addresses: , (comma, default), ; (semicolon), \n (new line), \t (tab) or | (pipe). Example: ;. One of: `,`, `;`, `
`, `	`, `|`.

Example input: `{"description":"<description>","emails":"<emails>"}`

### `everest_dmarc_domain_delete`

Remove DMARC Domain · Destructive

Remove a domain from DMARC monitoring.
Returns the deletion status.
Use everest_dmarc_domain_delete to stop monitoring a domain.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): The DMARC-monitored domain, without a scheme. Example: example.com.

Example input: `{"domain":"<domain>"}`

### `everest_inbox_test_delete`

Delete Inbox Test · Destructive

Delete an inbox placement test.
Returns the deletion status.
Use everest_inbox_test_delete to remove a test from the account for good.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `test_id` (`string`, required): ID of the inbox test, from everest_inbox_tests_list. Example: 3542086.

Example input: `{"test_id":"<test_id>"}`

### `everest_reputation_profile_delete`

Delete Reputation Profile · Destructive

Delete a reputation profile and stop monitoring its items. This cannot be undone.
Returns the deletion status.
Use everest_reputation_profile_delete to remove a profile. Use everest_reputation_profile_update with enabled 0 to pause it instead.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `profile_id` (`string`, required): ID of the reputation profile, from everest_reputation_profiles_list. Example: 1.

Example input: `{"profile_id":"<profile_id>"}`

### `everest_reputation_profile_item_delete`

Delete Reputation Profile Item · Destructive

Remove an item from a reputation profile.
Returns the deletion status.
Use everest_reputation_profile_item_delete to stop monitoring an IP or domain. Get the item ID from everest_reputation_profile_items_list.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `item_id` (`string`, required): ID of the profile item, from everest_reputation_profile_items_list. Example: 5.
- `profile_id` (`string`, required): ID of the reputation profile, from everest_reputation_profiles_list. Example: 1.

Example input: `{"item_id":"<item_id>","profile_id":"<profile_id>"}`

## Related

Other Marketing connectors ([all 190](/agentkit/connectors/?category=marketing)):

- [HubSpot](/agentkit/connectors/hubspot/): Scalekit connector, OAuth, 457 tools
- [Mailchimp](/agentkit/connectors/mailchimp/): Scalekit connector, OAuth, 73 tools
- [Twitter / X](/agentkit/connectors/twitteroauth/): Scalekit connector, OAuth, 92 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
