x402-agent-tools.nerolabs.workers.dev

https://x402-agent-tools.nerolabs.workers.dev/email-check

Shares a payout wallet with 31 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.

Checks one email address and returns valid, risky or invalid with the reasons: address format, whether the domain can receive mail (live MX lookup), known throwaway domains (mailinator and others, invalid), shared inboxes like info@ or sales@ (risky), likely typos such as gmial.com with the fix in didYouMean, and free providers such as gmail.com (flag only). Does not ping the mailbox (no SMTP), so valid is not a delivery guarantee.

30
reliability

Reliability & health

Uptime and response time from our own unpaid probes, plus the reliability score built from them.

Uptime

0.0% avg
0% 50% 100% Wed 1 PMSat 2 AMMon 11 AM

Response time

0ms 50ms 100ms Wed 1 PMSat 2 AMMon 11 AM
Data table
Reliability history per time bucket over the last 7 days (hourly).
Bucket Uptime Probes Response time
11/11/2026, 1:00:00 PM 0% 1 —
11/14/2026, 2:00:00 AM 0% 1 —
11/16/2026, 11:00:00 AM 0% 1 —
30
Composite reliability — the weighted average of the dimensions below, on a 0–100 scale.
Availability
0

How often it was reachable when we probed it (weight 35%).

Latency
not yet measured

How quickly it answers when it is up — fast scores high (weight 20%).

Security
100

Whether it serves over working TLS / https (weight 15%).

Transparency
55

Whether the operator disclosed what it does — description, schema, identity (weight 15%).

Activity
11

Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).

Confidence 28% — how much probe evidence backs this score. A thin history is flagged, not hidden.

See the scoring methodology for exactly how each number is computed.

Payment

Currencies
USDC
Networks
base
Facilitator
unknown
SDK
unknown

Operator

Company
inferred — unknown
Jurisdiction
—
Registrar
—
Domain registered
—
Hosting network
—
Hosting country
—

Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.

On-chain activity (base)

172
payments (30d)
6.42
USD volume (30d)
22
paying wallets (30d)

Payments per day

last payment 11/18/2026
0 45 90 Oct 21Oct 28Nov 6Nov 18
Data table
Settled payments per day.
Day Payments Volume (USD) Paying wallets
10/21/2026 82 1.66 3
10/22/2026 7 0.03 4
10/23/2026 2 0.02 2
10/25/2026 9 0.02 5
10/26/2026 3 0.02 1
10/27/2026 1 0 1
10/28/2026 2 0 1
10/29/2026 1 0.01 1
10/31/2026 1 0 1
11/1/2026 25 0.14 7
11/2/2026 8 0.09 6
11/3/2026 1 0.01 1
11/6/2026 2 0 2
11/8/2026 1 0 1
11/10/2026 1 0 1
11/11/2026 8 0.01 1
11/16/2026 5 0.01 1
11/17/2026 3 0 2
11/18/2026 10 4.38 2

Payout address changed 1 time, last on 10/22/2026

  • 0xbe39…7292 → 0xA969…164A (base) · 10/22/2026

A changed payout address is worth a second look — it can be routine, but it is also how a hijacked listing redirects funds.

This payout wallet is shared: figures cover all 32 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.

Response schema
{
  "properties": {
    "_example_note": {
      "type": "string"
    },
    "allReasons": {
      "items": {
        "type": "string"
      },
      "type": "array"
    },
    "didYouMean": {},
    "domain": {
      "type": "string"
    },
    "domainReceivesMail": {
      "type": "boolean"
    },
    "email": {
      "type": "string"
    },
    "isDisposable": {
      "type": "boolean"
    },
    "isFreeProvider": {
      "type": "boolean"
    },
    "isRoleAddress": {
      "type": "boolean"
    },
    "mailServer": {
      "type": "string"
    },
    "normalized": {
      "type": "string"
    },
    "note": {
      "type": "string"
    },
    "reason": {
      "type": "string"
    },
    "status": {
      "type": "string"
    },
    "syntaxValid": {
      "type": "boolean"
    }
  },
  "type": "object"
}