EmailGuard

What it does

Email validation API for AI agents. Validates one email per call: RFC 5322 syntax, disposable and temporary domain detection, role-based address, free-provider classification, typo suggestion (gnail.com -> gmail.com), plus-alias normalization to canonical form, and a deliverability score with per-rule evidence. Deterministic - the same record always gets the same answer - no data feed, no network calls. Loop it over your contact list to validate, dedupe, and normalize every record. Signed response receipt included.

• ✓RFC 5322, disposable, role & free-provider checks per record
• ✓Typo fix (gnail.com → gmail.com) + canonical normalization
• ✓Same record, same answer — loop whole lists at $0.02/record

Input schema

Top-level request fields. Nested shapes are shown in the example above and the OpenAPI spec.

How to call it over x402

1. 1. Send the request. The first unpaid call returns HTTP 402 with an x402 payment challenge — $0.02, USDC on Base, and the recipient.
2. 2. Pay per call. Your x402 client signs the USDC payment and retries automatically — no API key, no account, no subscription. New to x402?
3. 3. Read the result. HTTP 200 returns the computed values plus evidence-backed findings.

With the x402 fetch client (Node / TypeScript)

import { wrapFetchWithPayment } from "@x402/fetch";
import { privateKeyToAccount } from "viem/accounts";

const account = privateKeyToAccount(process.env.AGENT_WALLET_KEY);
const pay = wrapFetchWithPayment(fetch, account); // USDC on Base

const res = await pay("https://hermesplant.com/api/agent-services/emailguard/validate", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
  "email": "alice+work@gnail.com",
  "name": "Alice Example",
  "mxPresent": true
}),
});

const result = await res.json();

Inspect the 402 with curl

curl -i -X POST https://hermesplant.com/api/agent-services/emailguard/validate \
  -H "content-type: application/json" \
  -d '{"email":"alice+work@gnail.com","name":"Alice Example","mxPresent":true}'
# → HTTP/1.1 402 Payment Required  (x402 challenge: price, USDC asset, Base network, recipient)
# → sign the USDC-on-Base payment and retry to receive HTTP 200

Prefer no wallet? Get a free API key (250 calls/mo) and send it as X-API-Key instead of signing an x402 payment — the same call, no crypto, ideal for looping over many records.

Prefer zero code? This endpoint is also exposed as a tool on the Hermes Plant MCP server, so an MCP-capable agent can call it with its own x402 wallet.