polymarket crypto updown derived
blockrun.aiMarket dataderived
GET https://blockrun.ai/api/v1/pm/polymarket/crypto-updown
passlisted in Coinbase#36 by calls of 106 on this host
0.0085 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
- 14
- Unique payers, trailing 30 days
- 7
- Last called
- 2026-10-12 19:22 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.0085 USDC
- Networks
- 1
How has the volume on this endpoint moved?
polymarket crypto updown shares blockrun.ai with 105 other listed endpoints and is tied 36th by calls with 4 others.
polymarket crypto updown declares an input block that names no parameters.
The declared response carries data.
The registry's counters give polymarket crypto updown 14 calls and 7 unique payers over 30 days.
The last call to polymarket crypto updown came 1 day before the snapshot, 2026-10-12.
The declared price is 0.0085 USDC on Base.
polymarket crypto updown, a GET endpoint on blockrun.ai, appears in the Coinbase registry; TOLL's taxonomy puts it in market data.
polymarket crypto updown answered the sweep of 2026-10-27 with a valid 402, as at every sweep since 2026-09-11.
Closest in price to polymarket crypto updown within market data: chain tx at api.onesource.io and price at svm402.com.
polymarket crypto updown is priced above 39% of comparable listings in market data.
Across market data, 8,872 endpoints carry counters and polymarket crypto updown out-counts 92% of them.
58 listed endpoints across 2 hosts pay to the same wallet.
The seller's tags on polymarket crypto updown are ai, inference, llm and gateway.
50 other listings in market data declare exactly the same price.
the payment options, as of 2026-10-13 14:08 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.0085 USDC | exact | 0x6E0077…Ecb04c |
the checks, as of 2026-10-27 10:24 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-27 10:24 UTC | pass | 0 | daily-2026-10-27 |
| 2026-10-26 16:45 UTC | pass | 0 | daily-2026-10-26 |
| 2026-10-23 10:47 UTC | pass | 0 | daily-2026-10-23 |
| 2026-10-21 20:05 UTC | pass | 0 | daily-2026-10-21 |
| 2026-10-20 21:16 UTC | pass | 0 | daily-2026-10-20 |
| 2026-10-19 10:33 UTC | pass | 0 | daily-2026-10-19 |
| 2026-10-18 18:41 UTC | pass | 0 | daily-2026-10-18 |
| 2026-10-16 08:25 UTC | pass | 0 | daily-2026-10-16 |
| 2026-10-15 10:20 UTC | pass | 0 | daily-2026-10-15 |
| 2026-10-14 08:12 UTC | pass | 0 | daily-2026-10-14 |
| 2026-10-13 13:04 UTC | pass | 0 | daily-2026-10-13 |
| 2026-10-12 10:27 UTC | pass | 0 | daily-2026-10-12 |
| 2026-10-11 09:05 UTC | pass | 0 | daily-2026-10-11 |
| 2026-10-10 17:20 UTC | pass | 0 | daily-2026-10-10 |
| 2026-10-09 10:25 UTC | pass | 0 | daily-2026-10-09 |
| 2026-10-08 11:58 UTC | pass | 0 | daily-2026-10-08 |
| 2026-10-07 11:14 UTC | pass | 0 | daily-2026-10-07 |
| 2026-10-06 11:55 UTC | pass | 0 | daily-2026-10-06 |
| 2026-10-05 10:36 UTC | pass | 0 | daily-2026-10-05 |
| 2026-10-04 13:28 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-03 07:00 UTC | pass | 0 | daily-2026-10-03 |
| 2026-10-02 16:10 UTC | pass | 0 | daily-2026-10-02 |
| 2026-10-01 08:56 UTC | pass | 1 | daily-2026-10-01 |
| 2026-09-30 08:22 UTC | pass | 1 | daily-2026-09-30 |
| 2026-09-29 20:30 UTC | pass | 1 | daily-2026-09-29 |
| 2026-09-28 17:40 UTC | pass | 1 | daily-2026-09-28 |
| 2026-09-23 07:29 UTC | pass | 1 | daily-2026-09-23 |
| 2026-09-22 07:42 UTC | pass | 1 | daily-2026-09-22 |
| 2026-09-21 08:04 UTC | pass | 1 | daily-2026-09-21 |
| 2026-09-19 06:04 UTC | pass | 1 | daily-2026-09-19 |
| 2026-09-18 14:46 UTC | pass | 1 | daily-2026-09-18 |
| 2026-09-17 05:56 UTC | pass | 1 | daily-2026-09-17 |
| 2026-09-16 05:55 UTC | pass | 1 | daily-2026-09-16 |
| 2026-09-15 06:11 UTC | pass | 1 | daily-2026-09-15 |
| 2026-09-14 05:42 UTC | pass | 1 | daily-2026-09-14 |
| 2026-09-13 05:36 UTC | pass | 1 | daily-2026-09-13 |
| 2026-09-12 07:53 UTC | pass | 1 | daily-2026-09-12 |
| 2026-09-11 11:46 UTC | pass | 1 | 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-12 19:22 UTC · method · live
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {},
"discoverable": true
},
"output": {
"type": "json",
"example": {
"data": {}
}
}
}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, "polymarket crypto updown on blockrun.ai", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/blockrun-ai-api-v1-pm-polymarket-crypto-updown-adb3d2/at/2026-10-13T14-08Z. Accessed [access date].
BibTeX
@misc{toll-e-blockrun-ai-api-v1-pm-polymarket-crypto-updown-adb3d2-2026-10-13T14-08Z,
author = {TOLL},
title = {polymarket crypto updown on blockrun.ai},
howpublished = {\url{https://tollindex.com/e/blockrun-ai-api-v1-pm-polymarket-crypto-updown-adb3d2/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.