Skill: Email deliverability

Diagnose why a domain's email lands in spam: SPF posture, DMARC policy, DKIM key strength, MX targets, and a composite 0–100 score. Send POST /api/skill/email-deliverability with the required field domain and pay $0.009 per call over x402 or MPP (there is no free tier). It returns a JSON object with pack, args, steps and summary.

Email deliverability skill pack: one x402 payment runs 6 underlying tools (spf-check, dmarc-check, dkim-lookup, email-deliverability, email-validate, dns-lookup); partial-success per step.

Try in playground →

Parameters

Example request

curl -i -X POST https://agent402.tools/api/skill/email-deliverability \
  -H "Content-Type: application/json" \
  -d '{"domain":"example.com"}'

Without payment this returns HTTP 402 Payment Required with the exact price for skill-email-deliverability; any x402 v2 or MPP client pays it and retries.

Example response

{
  "pack": "email-deliverability",
  "args": {
    "domain": "example.com"
  },
  "steps": [
    {
      "slug": "spf-check",
      "ok": true,
      "result": {}
    },
    {
      "slug": "dmarc-check",
      "ok": true,
      "result": {}
    },
    {
      "slug": "dkim-lookup",
      "ok": true,
      "result": {}
    },
    {
      "slug": "email-deliverability",
      "ok": true,
      "result": {}
    },
    {
      "slug": "email-validate",
      "ok": true,
      "result": {}
    },
    {
      "slug": "dns-lookup",
      "ok": true,
      "result": {}
    }
  ],
  "summary": "6/6 steps succeeded"
}

From an MCP client

catalog.call {
  "slug": "skill-email-deliverability",
  "params": {
    "domain": "example.com"
  }
}

The hosted connector at https://agent402.tools/mcp needs a payment for skill-email-deliverability; the stdio package pays it from a wallet or from an AGENT402_CREDITS_KEY issued earlier. Local install: npx -y [email protected].

Errors and behavior

• Arguments left out fall back to the pack's own defaults. Each step reports on its own; the call succeeds when at least one step does, and a run where every step fails is refused (400 when the input caused it, 502 otherwise).
• A paid call that ends in any status of 400 or above is not charged over x402, MPP or a prepaid credits key: settlement runs after the tool and only on a successful response. The exception is a Tempo push credential, a transfer the buyer sent before the call: it settles before the tool runs, so if the tool then fails the payment is recorded as a refund owed to the paying wallet.
• Wallet-only: this tool reaches the network or stored state, so it has no proof-of-work tier. A prepaid card-credits key issued earlier (Authorization: Bearer a402_...) also pays it.
• A GET or HEAD to /api/skill/email-deliverability returns the same 402 quote, so the price can be read without a body.
• An Idempotency-Key header makes a retried paid call replay the first 200 instead of charging again (an answer larger than 1 MB is not replayed).

Paid call (JavaScript agent)

import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

const client = new x402Client();
client.setSpendControls?.({ maxAmountPerPayment: "$0.009" }); // refuse any quote above this tool's price
registerExactEvmScheme(client, { signer: privateKeyToAccount(KEY) });
const payFetch = wrapFetchWithPayment(fetch, client);

const res = await payFetch("https://agent402.tools/api/skill/email-deliverability", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    "domain": "example.com"
  }),
});

Related tools