passlisted in Coinbase#2 by calls of 3 on this host
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
- 6
- Unique payers, trailing 30 days
- 3
- Last called
- 2026-10-11 23:04 UTC
- First observed by TOLLderived
- 2026-09-25
- Pricederived
- 0.01 USDC
- Networks
- 2
How has the volume on this endpoint moved?
tx guard, a POST endpoint on getrugshield.com, appears in the Coinbase registry; TOLL's taxonomy puts it in market data.
On Base, tx guard asks 0.01 USDC per call.
The request to tx guard is a json body with the field transaction.
tx guard accepts payment on Base and Solana, 2 options in all, to 2 different wallets.
tx guard declares nothing about its output; validate flags that as advisory, not a verdict.
tx guard answered the sweep of 2026-10-15 with a valid 402, as at every sweep since 2026-09-25.
Of getrugshield.com's 3 listings, tx guard ranks tied 2nd by calls with 1 other.
29% of the host's counted calls go to it.
tx guard drew 6 calls from 3 unique payers in the trailing 30 days.
The last call to tx guard came 2 days before the snapshot, 2026-10-11.
Closest in price to tx guard within market data: address current balance at api.nansen.ai and token safety at api.deepnets.ai.
tx guard is priced above 40% of comparable listings in market data.
Across market data, 8,872 endpoints carry counters and tx guard out-counts 83% of them.
The payee wallet is shared by 6 listings across 2 hosts.
The seller's tags on tx guard are solana, pre-sign, transaction-simulation and wallet-drainer.
tx guard dropped out of the registry at the pull of 2026-09-29 and was listed again on 2026-10-11.
The price of tx guard is declared by 2,674 other listings in market data too.
the payment options, as of 2026-10-13 14:08 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.01 USDC | exact | 0x97a566…c45e1F |
| Coinbase | solana: | USDC | 0.01 USDC | exact | HtuDjVom…Tuik5g |
the checks, as of 2026-10-15 12:24 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-15 12:24 UTC | pass | 1 | daily-2026-10-15 |
| 2026-10-14 10:16 UTC | pass | 1 | daily-2026-10-14 |
| 2026-10-13 15:35 UTC | pass | 1 | daily-2026-10-13 |
| 2026-10-12 12:41 UTC | pass | 1 | daily-2026-10-12 |
| 2026-09-25 19:28 UTC | pass | 0 | new-after-daily-2026-09-24 |
Presence in a registry, not liveness of the service (method). Newest first.
- back in Coinbase
- absence from Coinbase confirmed, rule v1
- absent from Coinbase at this pull
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-10-11 23:04 UTC · method · live
The input and output block
{
"input": {
"body": {
"transaction": "AIABAAEDAQIDBAUGBwgJCgsMDQ4PEBESExQVFhcYGRobHB0eHyAhIiMkJSYnKCkqKywtLi8wMTIzNDU2Nzg5Ojs8PT4/QAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAgIAAQwCAAAAAQAAAAAAAAAA"
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": null
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-10-13 14:08 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "tx guard on getrugshield.com", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/getrugshield-com-v1-tx-guard-f63273/at/2026-10-13T14-08Z. Accessed [access date].
BibTeX
@misc{toll-e-getrugshield-com-v1-tx-guard-f63273-2026-10-13T14-08Z,
author = {TOLL},
title = {tx guard on getrugshield.com},
howpublished = {\url{https://tollindex.com/e/getrugshield-com-v1-tx-guard-f63273/at/2026-10-13T14-08Z}},
year = {2026},
month = {10},
note = {Pinned view of the snapshot of 2026-10-13 14:08 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.