Email Validate
Railway is a full-stack cloud for deploying web apps, servers, databases, and more with automatic scaling, monitoring, and security.
DataLiveeip155:8453Exactvia cdp
Email validateEmail validationValidate emailEmail verificationEmail verify
Calls · 30d
2
This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 5 snapshots so far.
$0.36
Verified settled volume
13 settlements proven x402 by their on-chain EIP-3009 marker.
$0.0010
Listed price
As published in the catalog. Always read the live 402 before paying.
3
Calls · 30d
Upstream's own call count for this endpoint, not ours.
1
Unique payers · 30d
Last called 2026-09-24 03:46Z
—
Upstream on-chain volume
Reported by the source catalog.
Paid to
0x0b4242adf40726d9b09688030948176752d29924The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.
Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
Provider
The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.
Accepts
The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.
0.001USDC≈ $0.001 USD
on Base · exact scheme
Pay 0.001 USDC on Base to 0x0b42…29924. The signed payment is good for 5 minutes.
- Paid to
- 0x0b42…29924
- USD Coin contract
- 0x8335…02913
- Payment window
- 5 minutes
- As published
- 1000 smallest units
The catalog’s raw entry
[
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0x0b4242adf40726d9b09688030948176752d29924",
"amount": "1000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 300
}
]Extensions
{
"bazaar": {
"info": {
"input": {
"body": {
"email": "hello@example.com"
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"note": "This assesses address/domain risk; it does not guarantee that a mailbox exists or will accept mail.",
"risk": "medium",
"email": "hello@example.com",
"mx_present": true,
"spf_present": true,
"reason_codes": [
"role_address"
],
"role_address": true,
"syntax_valid": true,
"dmarc_present": true,
"domain_exists": true,
"disposable_domain": false
}
}
},
"schema": {
"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",
"maxLength": 320,
"minLength": 3,
"description": "Email address to analyze for risk signals."
}
},
"additionalProperties": false
},
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"POST",
"PUT",
"PATCH"
],
"type": "string"
},
"bodyType": {
"enum": [
"json",
"form-data",
"text"
],
"type": "string"
}
},
"additionalProperties": false
},
"output": {
"type": "object",
"required": [
"type"
],
"properties": {
"type": {
"type": "string"
},
"example": {
"type": "object",
"properties": {
"note": {
"type": "string",
"description": "Honesty note: does not prove mailbox existence."
},
"risk": {
"enum": [
"low",
"medium",
"high"
],
"type": "string",
"description": "Aggregated risk label from the signals above."
},
"email": {
"type": "string",
"description": "Normalized email address assessed."
},
"mx_present": {
"type": "boolean",
"description": "Whether MX records exist for the domain."
},
"spf_present": {
"type": "boolean",
"description": "Whether TXT records exist (proxy for SPF presence check)."
},
"reason_codes": {
"type": "array",
"items": {
"type": "string"
},
"description": "Machine-readable codes explaining the risk label."
},
"role_address": {
"type": "boolean",
"description": "True if local-part looks like a role account (info, admin, …)."
},
"syntax_valid": {
"type": "boolean",
"description": "Whether the address matches a basic RFC-ish syntax regex."
},
"dmarc_present": {
"type": "boolean",
"description": "Whether _dmarc.<domain> has TXT records."
},
"domain_exists": {
"type": "boolean",
"description": "Whether the domain resolves (A/AAAA/MX)."
},
"disposable_domain": {
"type": "boolean",
"description": "True if domain is on a small known disposable list."
}
}
}
}
}
}
}
}
}Provenance
- Seen in the source catalog
- 2026-09-24 03:46Z
- Last indexed by Roundhouse
- 2026-09-24 07:30Z
- Last enriched (probe, favicon, geo)
- 2026-09-19 21:45Z
- x402 version
- 2
- Max timeout
- 300s
- Liveness probe
- HTTP 405
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.
GET api.roundhouseai.io/v0/endpoints
This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 5 snapshots so far. Verified volume counts only settlements with an on-chain EIP-3009 marker.
Show the promptHide the prompt
Using Roundhouse, look up the x402 service Email Validate and tell me whether it is worth paying: what a call costs, whether the endpoint answered when last probed, and what its payment record actually shows. curl -s 'https://api.roundhouseai.io/v0/endpoints?q=Email%20Validate' curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>' Then call it: read the price from the live 402 at https://agent-vending-production.up.railway.app/v1/email-risk, never from a cached figure, and pay with an x402 client. The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402, or use an organization key from https://roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.