Lead Email Verify

What it runs

1. 1
   Email Validation

   Source: Algorithmic (syntax) + DNS protocol (MX record verification)

2. 2
   DNS Lookup

   Source: DNS protocol (authoritative nameservers)

3. 3
   Domain Reputation

   Source: Threat intelligence feeds (multi-source scoring)

The answer returns every step’s result, so your agent can show or check each one.

Inputs

How to call it

# Needs an API key. The whole check is charged once, at the listed price.
curl -X POST https://api.strale.io/v1/solutions/lead-email-verify/execute \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "inputs": {
      "email": "test@google.com"
    },
    "max_price_cents": 20
  }'

# No account. The first request answers 402 with the price in USDC;
# an x402 client pays it from your wallet and repeats the request.
curl -i -X POST https://api.strale.io/x402/v2/solutions/lead-email-verify \
  -H 'Content-Type: application/json' \
  -d '{
    "email": "test@google.com"
  }'

The bundle’s published example input.

Limitations

• Disposable email detection covers major providers but new throwaway domains may not be flagged

  From step: Email Validation

  What to do instead: Check the domain’s age when investigating suspicious traffic.

• No mailbox is contacted. A made-up or bouncing address can return valid if its syntax is correct, its domain has mail servers, and it is not flagged as disposable. Catch-all domains are one example; mailbox existence and delivery are never checked.

  From step: Email Validation

  What to do instead: Require confirmation through a verification link before relying on a mailbox.

• Results reflect current DNS propagation — recent changes may take up to 48 hours to appear

  From step: DNS Lookup

  What to do instead: Query the authoritative nameserver directly (returned in the NS records) to see changes before full propagation

• Reputation scores aggregate multiple blocklists — a single listing may not indicate actual malicious activity

  From step: Domain Reputation

  What to do instead: Check which specific blocklist flagged the domain in the response details and verify the listing reason before blocking

• Blocklist data refreshed daily — recently resolved issues may still show negative reputation for 24-48 hours

  From step: Domain Reputation

  What to do instead: If a domain was recently cleaned, re-check after 48 hours and use the trend direction to assess improvement