Email x402 REST usage
Find email address for a person synchronously. Provide name + company or LinkedIn URL.
View daily earnings, market cap, volume and coverage →
email.intel.rallylive.ca · email.intel.rallylive.ca · Comms & Messaging
| Day · UTC | Earned | Gross volume | Refunds | Observed transfers | Market cap | Revenue coverage |
|---|---|---|---|---|---|---|
| 2026-10-26 | — | — | — | — | — | none |
| 2026-10-25 | — | — | — | — | — | none |
| 2026-10-24 | — | — | — | — | — | none |
| 2026-10-23 | — | — | — | — | — | none |
| 2026-10-22 | — | — | — | — | — | none |
| 2026-10-21 | — | — | — | — | — | none |
| 2026-10-20 | — | — | — | — | — | none |
View daily history → · UTC days; today's figures are partial.
Is the domain's email hosted by forwardemail? Looks up the MX records (Cloudflare DoH) and matches them against forwardemail's mail-exchanger patterns, returning yes/no, the MX hosts and which matched. Provider detection for deliverability, sales and migration work. $0.01 per lookup.
Quoted from x402 Bazaar · source record · read 2026-10-26
No settled payment on record. Earnings for this service are unknown — not zero. The source counts 1 calls in 30 days, which at the published price is roughly $0.01 of activity. Activity is not revenue; no charge has been reconciled for it.
A payment rail is where the provider asks to be paid. It is not proof that anything was paid through it. See evidence levels.
{
"method": "GET",
"queryParams": {
"domain": "github.com"
},
"type": "http"
}
{
"example": {
"domain": "github.com",
"hosted_here": false,
"mx": [
"\u2026"
],
"provider": "forwardemail"
},
"type": "json"
}
Examples are the provider's own, not a call we made.
One row per statement. “Verified” means we checked it ourselves and the finding is quoted. “Provider claim” means we read it in the provider's own record. “Not found” is a statement about our search, not proof of absence.
| Statement | Status | What we found | Source | Checked |
|---|---|---|---|---|
| Endpoint | Provider claim |
https://email.intel.rallylive.ca/email/hosted-by/forwardemail
EvidenceAls Resource-URL im Bazaar-Eintrag geführt. |
api.cdp.coinbase.com | 2026-10-26 |
| Input output | Provider claim |
Request/response examples published with the listing
EvidenceBeispiel-Ein- und -Ausgabe stammen aus dem Bazaar-Eintrag des Anbieters. |
api.cdp.coinbase.com | 2026-10-26 |
| Payment | Provider claim |
2 rails: Base, Base Sepolia · payee 0xFC24FD34da9e49A0110DCaEe3Ad30eC54175eBB3
EvidenceAus den `accepts`-Einträgen: Netzwerk, Asset, Empfängeradresse und Betrag. Die Adresse ist die Grundlage der späteren On-Chain-Zuordnung; sie ist noch nicht durch eine eigene 402-Antwort bestätigt. |
api.cdp.coinbase.com | 2026-10-26 |
| Pricing | Provider claim |
0.01 USDC per call
EvidenceAtomic amount 10000 = 0.01 USDC per call on Base. 2 payment options published. Netzwerk: Base, Base Sepolia. |
api.cdp.coinbase.com | 2026-10-26 |
| Protocol | Provider claim |
x402 (HTTP 402 payment challenge)
EvidenceIm x402 Bazaar als zahlungspflichtige HTTP-Ressource gelistet (x402Version 2, Typ http). |
api.cdp.coinbase.com | 2026-10-26 |
| Provider | Provider claim |
email.intel.rallylive.ca
EvidenceDie Ressource wird unter diesem Host im x402 Bazaar geführt; die Angaben stammen vom Anbieter. |
api.cdp.coinbase.com | 2026-10-26 |
| Reachability | Verified |
HTTP 402 · 457 ms
EvidenceEigene Anfrage am 2026-10-24 um 22:45 UTC an https://email.intel.rallylive.ca/email/hosted-by/forwardemail (GET, ohne Anmeldung, ohne Bezahlung). Antwort: HTTP 402 mit Zahlungsaufforderung. |
email.intel.rallylive.ca | 2026-10-24 |
| Usage | Verified |
1 calls / 1 unique payers in the last 30 days
EvidenceSource-reported usage from Coinbase x402 Bazaar, read on 2026-10-26. Letzter Aufruf laut Quelle: 2026-10-01T14:49:52.05Z. Aufrufe sind kein Umsatz. |
api.cdp.coinbase.com | 2026-10-26 |
| When | URL | Answer | Latency | Payment challenge |
|---|---|---|---|---|
| 2026-10-24 | https://email.intel.rallylive.ca/email/hosted-... | HTTP 402 · payment required | 457 ms |
0.01 USDC
eip155:8453
|
We call the documented URL once, unauthenticated and without paying. We never retry a payment challenge and never sign in.
Find email address for a person synchronously. Provide name + company or LinkedIn URL.
Extract public business emails, phone numbers, and social profiles from a website. Batch-safe contact enrichment for autonomous agents. Input: website URL. Returns structured JSON.
Validate an email address: RFC 5322 syntax, MX records, 5,361 disposable domain detection, role-based address detection (35 patterns), free provider detection, and typo suggestion for common providers (gmial.com ? gmail....
Profile enrichment from a name and company, an email, a phone or a profile URL. Phone lookup is off by default. include_phone=true adds the per-person add-on on the pricing page for up to one person; no phone hit is guar...
Chosen by category and by whether we have measured them, not by who pays us. A sponsored placement in this list is labelled as such.