Blockchain Data · x402 · early usage

Validate an email address in two layers: strict RFC-style syntax, then a live DNS MX lo…

Validate an email address in two layers: strict RFC-style syntax, then a live DNS MX lookup on the domain to confirm the recipient actually runs mail servers. Catches the typos and fake domains that pure regex misses. Use this when an agent needs to syntax +…

by agentstoolshub.com · discovered, not yet claimed by its owner · updated 2026-10-11

30d calls2

30d payers2

MethodGET

Outputjson

Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.

What it does

Tags: dev · crypto-dev · analytics · bazaar

Call contract

Method: GET
Input: query parameters
Output: json
Last paid call: 2026-10-11

Input example from Bazaar metadata

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

Output example

{
  "result": {
    "answer": "live data — call the API",
    "value": null
  },
  "tool": "email-validator"
}

Use with an agent

Discover. Agents find this listing with GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP tool search_resources, or /discovery/resources.
Inspect. Fetch /resources/35433.json for the price and payment options.
Pay. Call GET https://agentstoolshub.com/api/v1/dev/email-validator. The provider answers 402 with its payment requirements. An x402 client signs one of the options below and retries with PAYMENT-SIGNATURE.
Execute. The provider returns 200 with the data. Agent Bazaar is not in the request path and never sees your payment.

For humans

You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.

Pricing & payment

Price: $0.002 / request
Protocol: x402 v2
Auth: No account or API key. Pay per request.
Networks: Base
Demand: 2 calls · 2 unique payers in 30d (public x402 Bazaar data)

x402 payment requirements

Scheme	Network	Asset	Amount	Pay to	Timeout
exact	Base eip155:8453	USDC	$0.002	0x8a0F2b0a6C82D1c54B16E2e4DEcd18fF0802b0f6	300s

accepts[] (raw JSON)

[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "payTo": "0x8a0F2b0a6C82D1c54B16E2e4DEcd18fF0802b0f6",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "2000",
    "amountUsd": 0.002,
    "maxTimeoutSeconds": 300
  }
]

Schemas

Output schema (JSON Schema)

{
  "properties": {
    "example": {
      "type": "object"
    },
    "type": {
      "type": "string"
    }
  },
  "required": [
    "type"
  ],
  "type": "object"
}

Example shape — generated from the schema, not a captured live response

{
  "example": {},
  "type": "string"
}

Examples

curl

curl "https://agentstoolshub.com/api/v1/dev/email-validator"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paid

JavaScript

const res = await fetch("https://agentstoolshub.com/api/v1/dev/email-validator");
if (res.status === 402) {
  const { accepts } = await res.json();
  // pay one of accepts[] via an x402 client, then retry with the payment header
}

Python

import httpx
res = httpx.get("https://agentstoolshub.com/api/v1/dev/email-validator")
if res.status_code == 402:
    accepts = res.json()["accepts"]
    # pay one of accepts[] via an x402 client, then retry with the payment header

Details

Provider: agentstoolshub.com
Endpoint: https://agentstoolshub.com/api/v1/dev/email-validator
Machine-readable: /resources/35433.json