78trust / 100

Email Risk

by Email Validate in Email & messaging

x402 APIPassing, checked 29 min ago

Validate an email address using syntax, MX, disposable-domain, role-account, and domain-risk checks. Returns structured validation data for agent workflows, signup hygiene, and lead-quality checks. Does not guarantee that an individual mailbox exists.

POST https://agent-vending-production.up.railway.app/v1/email-risk

Last 30 days

All checks passedSome failedAll failedNot checked
Uptime
100%
Response time
358 ms typical, 423 ms slowest 5%
Last check
29 min ago
Next check
in 1 min

How to call it

# See the payment challenge (nothing is charged)
curl -i -X POST "https://agent-vending-production.up.railway.app/v1/email-risk" \
  -H "content-type: application/json" \
  -d '{"email":"[email protected]"}'
import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { ExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

const client = new x402Client().register(
  "eip155:8453",
  new ExactEvmScheme(privateKeyToAccount(process.env.AGENT_KEY)),
);
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? Preflight it first for $0.005:
// GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fagent-vending-production.up.railway.app%2Fv1%2Femail-risk
const res = await pay("https://agent-vending-production.up.railway.app/v1/email-risk", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({"email":"[email protected]"}),
});
console.log(await res.json());

Example input

{
  "email": "[email protected]"
}

Example output

{
  "disposable_domain": false,
  "dmarc_present": true,
  "domain_exists": true,
  "email": "[email protected]",
  "mx_present": true,
  "note": "This assesses address/domain risk; it does not guarantee that a mailbox exists or will accept mail.",
  "reason_codes": [
    "role_address"
  ],
  "risk": "medium",
  "role_address": true,
  "spf_present": true,
  "syntax_valid": true
}

Security scan

  • No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
29 min agoPassed402358 ms$0.001
5 h agoPassed402334 ms$0.001
8 h agoPassed402338 ms$0.001
12 h agoPassed402429 ms$0.001
15 h agoPassed402340 ms$0.001
18 h agoPassed402372 ms$0.001
23 h agoPassed402423 ms$0.001