# mailcheck.hugen.tokyo Email Validator

> mailcheck.hugen.tokyo Email Validator is a paid API for AI agents from mailcheck.hugen.tokyo, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Validates an email address using 6 checks (syntax, MX, disposable, free provider, role-based, typo) and returns a 0-1 confidence score

## Facts

- Endpoint: POST https://mailcheck.hugen.tokyo/mailcheck/validate
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mailcheck-hugen-tokyo-bd4922c3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1j38-5hA8iIFbjksCC873

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability mailcheck-hugen-tokyo-bd4922c3 -d '<json body>'
```

Example prompt: Can you validate the email address 'john.doe@gmial.com' for me — check if the syntax is correct, whether mail servers exist for the domain, and whether it looks disposable or role-based, and give me the confidence score?

## When to prefer this

Choose this endpoint when you need a single-call, multi-faceted email validation that covers syntax, DNS/MX, disposable detection, free-provider identification, role-address flagging, and typo correction all at once — without managing API keys or stitching together multiple services. Particularly valuable for user signup flows, lead qualification, or any agentic workflow where email quality matters and you want a simple 0-1 confidence score with per-check detail.

## Known failure modes

- Malformed request body returns 400 error
- Network issues reaching MX DNS servers may cause incomplete MX check
- Newly created disposable domains not yet in the 5000+ domain list may pass disposable check
- Payment failure (non-payment or wrong amount) returns 402 Payment Required
- Domain with no publicly resolvable MX records flagged as invalid even if domain exists

## How this service works

6 email validation checks in one call — syntax (RFC 5322), MX record verification, disposable detection (5,000+ domains), free provider identification, role-based address detection (admin@, info@), and typo suggestion. Returns a 0-1 confidence score with detailed per-check results. POST method protects email addresses from access logs. No API keys, no multiple service integrations needed. Accepts USDC payments on Base and Solana

## Output

Returns a JSON object with: overall score (0-1), domain, status (valid/invalid), is_free boolean, mx_found boolean, mx_records array, did_you_mean typo suggestion string, syntax_valid boolean, is_disposable boolean, is_role_based boolean, and a list of checks_performed.

## Example request

```json
{
 "email": "john.doe@gmial.com"
}
```

## Request schema (JSON Schema)

```json
{
 "properties": {
  "input": {
   "required": [
    "method"
   ]
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/mailcheck-hugen-tokyo-bd4922c3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mailcheck.hugen.tokyo](https://www.zero.xyz/host/mailcheck.hugen.tokyo/llms.txt)