# mailcheck.hugen.tokyo Email Validation

> mailcheck.hugen.tokyo Email Validation is a paid API for AI agents from mailcheck.hugen.tokyo, paid per call via x402, $0.005/call, status down (last checked 2026-09-15).

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

## Facts

- Endpoint: POST https://mailcheck.hugen.tokyo/validate
- Price: $0.005/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mailcheck-hugen-tokyo-996384a9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vFpH6DPEgHU07zgtfbiw5

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-996384a9 -d '<json body>'
```

Example prompt: Can you run a full validation check on 'john.doe@gmial.com' — I want to know if the syntax is valid, whether MX records exist, if it's a disposable or role-based address, and get a confidence score so I can decide whether to accept it for registration?

## When to prefer this

Choose this endpoint when you need comprehensive email validation in a single API call without managing multiple services or API keys. Ideal for user registration flows, lead qualification, or any scenario where you want to filter out disposable, role-based, or syntactically invalid emails while also catching common typos. The POST method is preferable when email privacy from access logs matters. Best when you need a single confidence score alongside granular per-check details.

## Known failure modes

- Invalid or missing email address input returns a validation error
- Domain has no MX records — MX check fails, lowering confidence score
- Network timeout during MX DNS lookup — partial results may be returned
- Malformed JSON request body returns HTTP 400
- Payment not included or insufficient USDC — HTTP 402 payment required

## 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 0-1 confidence score plus individual boolean/detail results for each of 6 checks: RFC 5322 syntax validity, MX record existence and hostnames, whether the domain is a known disposable provider (from 5,000+ domain list), whether it's a free email provider, whether the local part is role-based (e.g. admin@, info@), and a typo correction suggestion if the domain looks misspelled.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/mailcheck-hugen-tokyo-996384a9/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)