# Penniless Data Utilities – Email Validation

> Penniless Data Utilities – Email Validation is a paid API for AI agents from penniless-json-repair.sjaman.workers.dev, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Validates an email address by checking format syntax and performing a live DNS MX record lookup to confirm the domain can receive mail

## Facts

- Endpoint: POST https://penniless-json-repair.sjaman.workers.dev/email/validate
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/penniless-data-utilities-email-validation-facf70ff
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_EedKbGUtRcak31TwdeTwA

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 penniless-data-utilities-email-validation-facf70ff -d '<json body>'
```

Example prompt: Can you check whether hello@example.com is a valid, deliverable email address — make sure the format is correct and that the domain actually has MX records set up?

## When to prefer this

Choose this endpoint when you need lightweight, deterministic email validation that combines format checking with live DNS MX record verification, without relying on sending a confirmation email or calling an AI model. Ideal for pre-send list hygiene, signup form validation, or CRM auditing where you want a fast, cheap ($0.001 USDC) programmatic check. Prefer this over heavier deliverability services when you only need format + MX-level assurance rather than SMTP-level probing or inbox existence verification.

## Known failure modes

- Malformed or missing email input parameter returns an error response
- Domain with no DNS record returns domainHasMx: false and valid: false
- Temporary DNS resolution failure may return an error status rather than NOERROR
- Email with valid format but unresolvable TLD returns domainHasMx: false
- Payment failure via x402 micropayment results in 402 response before validation occurs

## How this service works

Deterministic, dependency-free data utilities served over x402 micropayments (USDC on Base). None of these call another AI model.
Keyword: JSON repair
Keyword: malformed JSON
Keyword: broken JSON from LLM
Keyword: fix JSON output
Keyword: JSON sanitizer
Keyword: truncated JSON recovery
Keyword: YAML to JSON
Keyword: convert YAML
Keyword: parse YAML config
Keyword: cron next run
Keyword: cron parser
Keyword: when does cron run next
Keyword: unified diff
Keyword: line diff
Keyword: text diff
Keyword: HTML to text
Keyword: extract links
Keyword: extract emails
Keyword: scrape text
Keyword: whois lookup
Keyword: domain registration
Keyword: registrar
Keyword: domain expiry date
Keyword: RDAP
Keyword: dns lookup
Keyword: MX records
Keyword: TXT records
Keyword: A record
Keyword: DNS over HTTPS
Keyword: github repo stats
Keyword: github stars
Keyword: repository popularity
Keyword: OSS project metadata
Keyword: email validation
Keyword: verify email address
Keyword: check MX deliverability
Keyword: email syntax
Use case: repair a JSON code block wrapped in Markdown fences
Use case: turn a docker-compose or CI YAML file into JSON
Use case: compute the next UTC fire time of a cron expression
Use case: produce a unified diff between two versions of a file
Use case: strip HTML tags and pull out links, emails, and headings
Use case: look up a domain's registrar, status and expiry before purchase
Use case: check when a domain registration lapses
Use case: resolve A, AAAA, MX, TXT or NS records for a hostname
Use case: find a domain's mail servers and SPF TXT record
Use case: compare GitHub repository stars, forks and activity for market research
Use case: check whether an email address is well-formed and its domain accepts mail

## Output

Returns a JSON object containing: the normalized email address, a boolean 'valid' overall result, 'formatValid' indicating syntax correctness, 'domainHasMx' indicating whether MX records exist, 'ok' for request success, the raw DNS 'status' (e.g. NOERROR), and an array of 'mx' records with host and preference values.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "required": [
      "email"
     ],
     "properties": {
      "email": {
       "type": "string",
       "description": "Email address"
      }
     },
     "additionalProperties": false
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "mx": [
   {
    "host": "",
    "preference": 0
   }
  ],
  "ok": true,
  "email": "hello@example.com",
  "valid": true,
  "status": "NOERROR",
  "domainHasMx": true,
  "formatValid": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/penniless-data-utilities-email-validation-facf70ff/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from penniless-json-repair.sjaman.workers.dev](https://www.zero.xyz/host/penniless-json-repair.sjaman.workers.dev/llms.txt)