passlisted in Coinbasecounted above 26% of Market data
0.01 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
- 2
- Unique payers, trailing 30 days
- 2
- Last called
- 2026-10-08 05:32 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.01 USDC
- Networks
- 1
How has the volume on this endpoint moved?
At api.wallettriage.com, scan takes GET requests, is listed in the Coinbase registry, and falls under market data by TOLL's rules.
Per call, scan declares 0.01 USDC on Base.
scan takes the query parameters chain and address.
A response from scan, as declared, includes chain, address, summary, findings, stateless, checked_at and 2 others.
scan answered the sweep of 2026-10-30 with a valid 402, as at every sweep since 2026-09-11.
scan is the only listed endpoint on api.wallettriage.com.
The registry's counters give scan 2 calls and 2 unique payers over 30 days, every call from a different payer.
scan was last called 24 days before the snapshot.
Closest in price to scan within market data: token price at api.kadec0.xyz and address current balance at api.nansen.ai.
scan is priced above 47% of comparable listings in market data.
Its payee wallet receives for this endpoint alone.
The seller's tags on scan are security, wallet-risk, approvals and threat-intel.
The price of scan is declared by 2,261 other listings in market data too.
the payment options, as of 2026-11-01 13:19 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.01 USDC | exact | 0x93835C…29Dacc |
the checks, as of 2026-10-30 09:36 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-30 09:36 UTC | pass | 0 | daily-2026-10-30 |
| 2026-10-29 09:16 UTC | pass | 0 | daily-2026-10-29 |
| 2026-10-28 09:38 UTC | pass | 0 | daily-2026-10-28 |
| 2026-10-27 09:21 UTC | pass | 0 | daily-2026-10-27 |
| 2026-10-26 15:48 UTC | pass | 0 | daily-2026-10-26 |
| 2026-10-23 09:35 UTC | pass | 0 | daily-2026-10-23 |
| 2026-10-21 12:05 UTC | pass | 0 | daily-2026-10-21 |
| 2026-10-20 11:43 UTC | pass | 0 | daily-2026-10-20 |
| 2026-10-19 09:22 UTC | pass | 0 | daily-2026-10-19 |
| 2026-10-18 11:12 UTC | pass | 0 | daily-2026-10-18 |
| 2026-10-16 07:23 UTC | pass | 0 | daily-2026-10-16 |
| 2026-10-15 09:12 UTC | pass | 0 | daily-2026-10-15 |
| 2026-10-14 07:12 UTC | pass | 0 | daily-2026-10-14 |
| 2026-10-13 11:58 UTC | pass | 0 | daily-2026-10-13 |
| 2026-10-12 09:22 UTC | pass | 0 | daily-2026-10-12 |
| 2026-10-11 08:01 UTC | pass | 0 | daily-2026-10-11 |
| 2026-10-10 16:09 UTC | pass | 0 | daily-2026-10-10 |
| 2026-10-09 08:58 UTC | pass | 0 | daily-2026-10-09 |
| 2026-10-08 10:25 UTC | pass | 0 | daily-2026-10-08 |
| 2026-10-07 09:49 UTC | pass | 0 | daily-2026-10-07 |
| 2026-10-06 10:36 UTC | pass | 0 | daily-2026-10-06 |
| 2026-10-05 09:29 UTC | pass | 0 | daily-2026-10-05 |
| 2026-10-04 11:42 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-03 06:19 UTC | pass | 0 | daily-2026-10-03 |
| 2026-10-02 15:31 UTC | pass | 0 | daily-2026-10-02 |
| 2026-10-01 08:21 UTC | pass | 0 | daily-2026-10-01 |
| 2026-09-30 07:43 UTC | pass | 0 | daily-2026-09-30 |
| 2026-09-29 19:56 UTC | pass | 0 | daily-2026-09-29 |
| 2026-09-28 17:00 UTC | pass | 0 | daily-2026-09-28 |
| 2026-09-25 21:26 UTC | pass | 0 | daily-2026-09-25 |
| 2026-09-23 06:59 UTC | pass | 0 | daily-2026-09-23 |
| 2026-09-22 07:11 UTC | pass | 0 | daily-2026-09-22 |
| 2026-09-21 07:33 UTC | pass | 0 | daily-2026-09-21 |
| 2026-09-19 05:35 UTC | pass | 0 | daily-2026-09-19 |
| 2026-09-18 14:03 UTC | pass | 0 | daily-2026-09-18 |
| 2026-09-17 05:28 UTC | pass | 0 | daily-2026-09-17 |
| 2026-09-16 05:28 UTC | pass | 0 | daily-2026-09-16 |
| 2026-09-15 05:45 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 05:17 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 05:13 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 07:29 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 11:15 UTC | pass | 0 | daily-2026-09-11 |
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-08 05:32 UTC · method · live
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"chain": "eth",
"address": "0x1111111111111111111111111111111111111111"
}
},
"output": {
"type": "json",
"example": {
"chain": "eth",
"address": "0x1111111111111111111111111111111111111111",
"summary": {
"spam_suppressed": 5,
"total_approvals": 42,
"low_noise_approvals": 34,
"low_value_at_risk_usd": 12.5
},
"findings": [
{
"type": "exploit_exposure",
"token": "USDC",
"detail": "Active approval involves a contract currently flagged by the live threat feed.",
"tokens": [
"USDC",
"WETH",
"DAI"
],
"spender": "0x2222222222222222222222222222222222222222",
"severity": "critical",
"usd_at_risk": 125000,
"affected_approvals": 3,
"recommended_action": "revoke_approval"
}
],
"stateless": true,
"checked_at": "2026-07-08T00:00:00.000Z",
"risk_level": "critical",
"risk_score": 96,
"threat_feed": {
"state": "ok",
"entities": 7,
"updated_at": "2026-07-08T00:00:00.000Z"
}
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-11-01 13:19 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "scan on api.wallettriage.com", snapshot of 2026-11-01 13:19 UTC. https://tollindex.com/e/api-wallettriage-com-scan-873bf4/at/2026-11-01T13-19Z. Accessed [access date].
BibTeX
@misc{toll-e-api-wallettriage-com-scan-873bf4-2026-11-01T13-19Z,
author = {TOLL},
title = {scan on api.wallettriage.com},
howpublished = {\url{https://tollindex.com/e/api-wallettriage-com-scan-873bf4/at/2026-11-01T13-19Z}},
year = {2026},
month = {11},
note = {Pinned view of the snapshot of 2026-11-01 13:19 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.