passlisted in Coinbase#22 by calls of 116 on this host
0.0025 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
- 5
- Unique payers, trailing 30 days
- 3
- Last called
- 2026-10-27 09:46 UTC
- First observed by TOLLderived
- 2026-10-04
- Pricederived
- 0.0025 USDC
- Networks
- 2
How has the volume on this endpoint moved?
Of 2s.io's 116 listings, crypto address validate ranks tied 22nd by calls with 2 others.
Its declared inputs are the query parameters chain and address.
crypto address validate declares nothing about its output; validate flags that as advisory, not a verdict.
Over 30 days: 5 calls, 3 payers.
crypto address validate was last called 5 days before the snapshot.
It is priced at 0.0025 USDC on Base.
crypto address validate accepts payment on Base and Solana, 2 options in all, to 2 different wallets.
At 2s.io, crypto address validate takes GET requests, is listed in the Coinbase registry, and falls under market data by TOLL's rules.
crypto address validate answered the sweep of 2026-10-30 with a valid 402, as at every sweep since 2026-10-04.
Closest in price to crypto address validate within market data: chain erc20 balance at api.onesource.io and stock at api.tickersfeed.net.
crypto address validate is priced above 19% of comparable listings in market data.
Across market data, 10,071 endpoints carry counters and crypto address validate out-counts 73% of them.
128 listed endpoints on one host pay to the same wallet.
The seller's tags on crypto address validate are public-records, identifiers, ai-agents and us-gov-data.
37 other listings in market data declare exactly the same price.
the payment options, as of 2026-11-01 05:59 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.0025 USDC | exact | 0x2b6D49…FC32C5 |
| Coinbase | solana: | USDC | 0.0025 USDC | exact | TW6ntaGz…YcyWhn |
the checks, as of 2026-10-30 11:14 UTC · method · pinnableendpoint answered HTTP 402
bazaar.info.output· advisory, does not affect the verdict · output metadata is present (advisory)
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-30 11:14 UTC | pass | 1 | daily-2026-10-30 |
| 2026-10-29 10:51 UTC | pass | 1 | daily-2026-10-29 |
| 2026-10-28 11:15 UTC | pass | 1 | daily-2026-10-28 |
| 2026-10-27 10:52 UTC | pass | 1 | daily-2026-10-27 |
| 2026-10-23 11:19 UTC | pass | 1 | daily-2026-10-23 |
| 2026-10-21 20:53 UTC | pass | 1 | daily-2026-10-21 |
| 2026-10-19 11:04 UTC | pass | 1 | daily-2026-10-19 |
| 2026-10-18 19:18 UTC | pass | 1 | daily-2026-10-18 |
| 2026-10-16 08:53 UTC | pass | 1 | daily-2026-10-16 |
| 2026-10-15 10:50 UTC | pass | 1 | daily-2026-10-15 |
| 2026-10-14 08:41 UTC | pass | 1 | daily-2026-10-14 |
| 2026-10-13 13:33 UTC | pass | 1 | daily-2026-10-13 |
| 2026-10-12 10:58 UTC | pass | 1 | daily-2026-10-12 |
| 2026-10-11 09:39 UTC | pass | 1 | daily-2026-10-11 |
| 2026-10-10 17:49 UTC | pass | 1 | daily-2026-10-10 |
| 2026-10-09 11:02 UTC | pass | 1 | daily-2026-10-09 |
| 2026-10-08 12:37 UTC | pass | 1 | daily-2026-10-08 |
| 2026-10-07 11:52 UTC | pass | 1 | daily-2026-10-07 |
| 2026-10-06 12:35 UTC | pass | 1 | daily-2026-10-06 |
| 2026-10-05 11:08 UTC | pass | 1 | daily-2026-10-05 |
| 2026-10-04 22:07 UTC | pass | 1 | new-after-daily-2026-10-04 |
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-27 09:46 UTC · method · live
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"chain": "eth",
"address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
}
},
"output": null
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-11-01 05: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, "crypto address validate on 2s.io", snapshot of 2026-11-01 05:59 UTC. https://tollindex.com/e/2s-io-api-crypto-address-validate-be3778/at/2026-11-01T05-59Z. Accessed [access date].
BibTeX
@misc{toll-e-2s-io-api-crypto-address-validate-be3778-2026-11-01T05-59Z,
author = {TOLL},
title = {crypto address validate on 2s.io},
howpublished = {\url{https://tollindex.com/e/2s-io-api-crypto-address-validate-be3778/at/2026-11-01T05-59Z}},
year = {2026},
month = {11},
note = {Pinned view of the snapshot of 2026-11-01 05:59 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.