ToolVet
75trust / 100

Email Verify Api

by AgentUtility.ai in Security & trust

x402 APIPassing, checked 3 h ago

Verifies an email address with syntax, MX, disposable-domain, role-account, SPF, DMARC, and DKIM checks. Same DNS-safe email deliverability backend as email-verify, indexed for agents searching exact email verification wording. Use it as an email verify API or to validate email address input.

POST
https://x402.agentutility.ai/email-verify-api
Price
$0.005
per call in USDC
Uptime
79.2%
last 30 days
Response time
153 ms
4.6 s slowest 5%
Last check
Passed
3 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

How to call it

POST https://x402.agentutility.ai/email-verify-api

Each call costs $0.005 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

POST https://x402.agentutility.ai/email-verify-api
content-type: application/json

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

Parameters

ParameterTypeRequiredDescription
dkim_selectorsarray of stringNoOptional DKIM selectors to check. Defaults to common selectors such as google, selector1, selector2, s1, and s2.
emailstringYesEmail address to validate and score, e.g. '[email protected]'.

Example response

The provider's example. We can't check it without paying.

{
  "can_receive_mail": true,
  "deliverability_score": 92,
  "risk": "low"
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.005.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://x402.agentutility.ai/email-verify-api' \
  -H 'content-type: application/json' \
  --data-raw '{"email":"[email protected]"}'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://x402.agentutility.ai/email-verify-api' \
  -H 'content-type: application/json' \
  --data-raw '{"email":"[email protected]"}' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.005 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.005" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.005 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fx402.agentutility.ai%2Femail-verify-api&method=POST
const res = await pay("https://x402.agentutility.ai/email-verify-api", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "email": "[email protected]"
  }),
});
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.005 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.005"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://x402.agentutility.ai/email-verify-api",
        json={
            "email": "[email protected]",
        },
    )
    print(res.status_code, res.text)

Security scan

No findings

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

Recent checks

WhenResultHTTPTimePrice
3 h agoPassed402138 ms$0.005
7 h agoPassed402117 ms$0.005
11 h agoPassed4027.2 s$0.005
15 h agoPassed402153 ms$0.005
19 h agoPassed402118 ms$0.005
Show 10 older checks
23 h agoTimed out---
27 h agoPassed4022.4 s$0.005
31 h agoPassed4022.3 s$0.005
34 h agoPassed402125 ms$0.005
38 h agoPassed40247 ms$0.005
42 h agoTimed out---
45 h agoPassed402165 ms$0.005
2 days agoPassed4023.0 s$0.005
2 days agoPassed402115 ms$0.005
2 days agoTimed out---