polygon should pay derived
47620.xyzMarket dataderived
GET https://47620.xyz/x/polygon/should-pay/:address
faillisted in Coinbase#50 by calls of 130 on this host
0.02 USDC
per call, as the listing declares it on solana:
- Validation state
- fail
- Uptime, 7 / 30 / 90 days
- 0% / 0% / 0%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-09-28 03:40 UTC
- First observed by TOLLderived
- 2026-09-28
- Pricederived
- 0.02 USDC
- Networks
- 3
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 1 time across 8 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.
At the sweep of 2026-09-30 it answered HTTP 200 rather than 402, so TOLL records it as failing.
polygon should pay, a GET endpoint on 47620.xyz, appears in the Coinbase registry; TOLL's taxonomy puts it in market data.
Per call, polygon should pay declares 0.02 USDC on Solana.
Its declared inputs are the path parameter address.
For polygon should pay the listing declares 3 accepts on Solana, Base and Polygon, to 2 different wallets.
polygon should pay returns json; the example shows ok, data and endpoint.
In the trailing 30 days: one call, one payer.
polygon should pay was last called 3 days before the snapshot.
47620.xyz lists 130 endpoints; polygon should pay is tied 50th by calls with 80 others.
It is cheaper than 32% of comparable listings in market data.
Closest in price to polygon should pay within market data: stonk alerts invoke at api.solenrich.com and analytics cost to quote at api.onesource.io.
The wallet paid by polygon should pay is the payee of 130 endpoints on one host.
The seller's own tags are polygon, Decision, Risk and Payments.
polygon should pay first appeared in TOLL's pulls on 2026-09-28.
Exactly this price appears on 620 other listings in market data.
the payment options, as of 2026-09-30 22:14 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | solana: | USDC | 0.02 USDC | exact | 8iZbjedT…Hm7j68 |
| Coinbase | eip155: | USDC | 0.02 USDC | exact | 0x7f4ce6…1B9d53 |
| Coinbase | eip155: | USDC | 0.02 USDC | exact | 0x7f4ce6…1B9d53 |
the checks, as of 2026-09-30 06:13 UTC · method · pinnableendpoint answered HTTP 200
returns_402· an unauthenticated request gets HTTP 402
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-09-30 06:13 UTC | fail | 1 | daily-2026-09-30 |
| 2026-09-29 18:34 UTC | fail | 1 | daily-2026-09-29 |
| 2026-09-28 05:33 UTC | fail | 1 | daily-2026-09-28 |
| 2026-09-28 05:31 UTC | fail | 1 | new-after-daily-2026-09-28 |
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-09-28 03:40 UTC · method · live
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"pathParams": {
"address": "0x7f4ce6C23F851F13b386EFdb22fE0d09821B9d53"
}
},
"output": {
"type": "json",
"example": {
"ok": true,
"data": {
"fetchedAt": "<iso>"
},
"endpoint": "polygon-should-pay"
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-09-30 22:14 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "polygon should pay on 47620.xyz", snapshot of 2026-09-30 22:14 UTC. https://tollindex.com/e/47620-xyz-x-polygon-should-pay-address-2d14c7/at/2026-09-30T22-14Z. Accessed [access date].
BibTeX
@misc{toll-e-47620-xyz-x-polygon-should-pay-address-2d14c7-2026-09-30T22-14Z,
author = {TOLL},
title = {polygon should pay on 47620.xyz},
howpublished = {\url{https://tollindex.com/e/47620-xyz-x-polygon-should-pay-address-2d14c7/at/2026-09-30T22-14Z}},
year = {2026},
month = {9},
note = {Pinned view of the snapshot of 2026-09-30 22:14 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.