passlisted in Coinbase#2 by calls of 12 on this host
0.003 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 17
- Unique payers, trailing 30 days
- 7
- Last called
- 2026-10-30 01:19 UTC
- First observed by TOLLderived
- 2026-10-02
- Pricederived
- 0.003 USDC
- Networks
- 2
How has the volume on this endpoint moved?
verify email is one of 12 listed endpoints on resolve402.dev, 2nd by calls among them.
Requests carry the query parameter email.
verify email returns json; the example shows email, score, has_mx, reasons, accept_all, score_band and 2 others.
verify email drew 17 calls from 7 unique payers in the trailing 30 days.
The last call to verify email came 3 days before the snapshot, 2026-10-30.
On Base, verify email asks 0.003 USDC per call.
20% of the host's counted calls go to it.
For verify email the listing declares 2 accepts on Base and Solana, to 2 different wallets.
TOLL files verify email under identity: a GET endpoint on resolve402.dev, listed in the Coinbase registry.
verify email answered the sweep of 2026-10-31 with a valid 402, as at every sweep since 2026-10-02.
Closest in price to verify email within identity: tools verify semaphore at x402.freeq.one and cambio at brasil-dados-api.onrender.com.
Among comparable prices in identity, verify email sits above 16% of them.
verify email out-counts 95% of the 2,489 endpoints in identity that carry counters.
The wallet paid by verify email is the payee of 12 endpoints on one host.
Seller tags: email, email-verification, email-validation and verify-email.
The price of verify email is declared by 111 other listings in identity too.
the payment options, as of 2026-11-01 21:59 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.003 USDC | exact | 0x30cd7C…6Fcba9 |
| Coinbase | solana: | USDC | 0.003 USDC | exact | 55qfRaRi…UNbbkK |
the checks, as of 2026-10-31 21:00 UTC · method · pinnableendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-31 21:00 UTC | pass | 0 | daily-2026-10-31 |
| 2026-10-30 06:28 UTC | pass | 0 | daily-2026-10-30 |
| 2026-10-29 06:10 UTC | pass | 0 | daily-2026-10-29 |
| 2026-10-28 06:33 UTC | pass | 0 | daily-2026-10-28 |
| 2026-10-27 06:26 UTC | pass | 0 | daily-2026-10-27 |
| 2026-10-26 11:47 UTC | pass | 0 | daily-2026-10-26 |
| 2026-10-24 21:09 UTC | pass | 0 | daily-2026-10-24 |
| 2026-10-23 06:19 UTC | pass | 0 | daily-2026-10-23 |
| 2026-10-22 04:34 UTC | pass | 0 | daily-2026-10-22 |
| 2026-10-21 08:13 UTC | pass | 0 | daily-2026-10-21 |
| 2026-10-20 08:28 UTC | pass | 0 | daily-2026-10-20 |
| 2026-10-19 06:02 UTC | pass | 0 | daily-2026-10-19 |
| 2026-10-18 08:16 UTC | pass | 0 | daily-2026-10-18 |
| 2026-10-17 18:17 UTC | pass | 0 | daily-2026-10-17 |
| 2026-10-16 04:30 UTC | pass | 0 | daily-2026-10-16 |
| 2026-10-15 06:04 UTC | pass | 0 | daily-2026-10-15 |
| 2026-10-14 04:28 UTC | pass | 0 | daily-2026-10-14 |
| 2026-10-13 08:54 UTC | pass | 0 | daily-2026-10-13 |
| 2026-10-12 06:18 UTC | pass | 0 | daily-2026-10-12 |
| 2026-10-11 04:41 UTC | pass | 0 | daily-2026-10-11 |
| 2026-10-10 09:59 UTC | pass | 0 | daily-2026-10-10 |
| 2026-10-09 04:44 UTC | pass | 0 | daily-2026-10-09 |
| 2026-10-08 06:21 UTC | pass | 0 | daily-2026-10-08 |
| 2026-10-07 05:32 UTC | pass | 0 | daily-2026-10-07 |
| 2026-10-06 06:27 UTC | pass | 0 | daily-2026-10-06 |
| 2026-10-05 06:10 UTC | pass | 0 | daily-2026-10-05 |
| 2026-10-04 08:59 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-03 04:17 UTC | pass | 0 | daily-2026-10-03 |
| 2026-10-02 22:16 UTC | pass | 0 | new-after-daily-2026-10-02 |
Presence in a registry, not liveness of the service (method). Newest first.
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-10-30 01:19 UTC · method · live
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"email": "jane@acme.fr"
}
},
"output": {
"type": "json",
"example": {
"email": "jane@acme.fr",
"score": 90,
"has_mx": true,
"reasons": [
{
"code": "mx_present",
"detail": "Domain has 2 MX record(s).",
"points": 30
}
],
"accept_all": null,
"score_band": "good",
"smtp_check": false,
"deliverable": "likely",
"syntax_valid": true,
"mail_provider": "google_workspace",
"mailbox_checked": false
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-11-01 21:59 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "verify email on resolve402.dev", snapshot of 2026-11-01 21:59 UTC. https://tollindex.com/e/resolve402-dev-api-verify-email-1b2035/at/2026-11-01T21-59Z. Accessed [access date].
BibTeX
@misc{toll-e-resolve402-dev-api-verify-email-1b2035-2026-11-01T21-59Z,
author = {TOLL},
title = {verify email on resolve402.dev},
howpublished = {\url{https://tollindex.com/e/resolve402-dev-api-verify-email-1b2035/at/2026-11-01T21-59Z}},
year = {2026},
month = {11},
note = {Pinned view of the snapshot of 2026-11-01 21:59 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.