legacy v1listed in Coinbase#1 by calls of 6 on this host
0.01 USDC
per call, as the listing declares it on eip155:
- Validation state
- legacy v1
- Uptime, 7 / 30 / 90 days
- 0% / 0% / 0%
- Calls, trailing 30 days
- 4
- Unique payers, trailing 30 days
- 3
- Last called
- 2026-09-14 20:03 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.01 USDC
- Networks
- 1
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 2 times across 29 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-15 it answered with the x402 v1 protocol, which the registry no longer indexes.
TOLL files scrape under scraping: a GET endpoint on cryptorisk-api.vercel.app, listed in the Coinbase registry.
On Base, scrape asks 0.01 USDC per call.
The request to scrape is the query parameters url, format and max_chars.
A response from scrape, as declared, includes url, chars, title, format, status, content and 2 others.
The registry's counters give scrape 4 calls and 3 unique payers over 30 days.
scrape was last called 1 day before the snapshot.
With 6 endpoints listed on cryptorisk-api.vercel.app, scrape is tied 1st by calls with 1 other.
It accounts for 24% of the calls counted across the host.
scrape is priced above 30% of comparable listings in scraping.
The nearest comparably priced alternatives in scraping are firecrawl scrape on vaaya.ai and extract on schemasure.com.
Its payee wallet receives for 13 listed endpoints across 2 hosts.
scrape out-counts 70% of the 615 endpoints in scraping that carry counters.
The price of scrape is declared by 194 other listings in scraping too.
the payment options, as of 2026-09-15 21:20 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.01 USDC | exact | 0xE0Ed7A…bB83de |
the checks, as of 2026-09-15 06:37 UTC · method · pinnableendpoint answered HTTP 402
x402_version· the body declares x402 version 2
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-09-15 06:37 UTC | legacy v1 | 1 | daily-2026-09-15 |
| 2026-09-14 06:05 UTC | legacy v1 | 1 | daily-2026-09-14 |
| 2026-09-13 05:57 UTC | legacy v1 | 1 | daily-2026-09-13 |
| 2026-09-12 08:14 UTC | legacy v1 | 1 | daily-2026-09-12 |
| 2026-09-11 12:40 UTC | legacy v1 | 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-09-14 20:03 UTC · method · live
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"url": "Absolute URL to fetch. Required.",
"format": "markdown | text | html. Default markdown.",
"max_chars": "Truncation limit, default 40000, max 120000."
}
},
"output": {
"type": "json",
"example": {
"url": "https://example.com/article",
"chars": 1840,
"title": "Example Article",
"format": "markdown",
"status": 200,
"content": "# Example Article ...clean markdown...",
"truncated": false,
"latency_ms": 620,
"description": "meta description text"
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-09-15 21:20 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "scrape on cryptorisk-api.vercel.app", snapshot of 2026-09-15 21:20 UTC. https://tollindex.com/e/cryptorisk-api-vercel-app-api-scrape-d11cdb/at/2026-09-15T21-20Z. Accessed [access date].
BibTeX
@misc{toll-e-cryptorisk-api-vercel-app-api-scrape-d11cdb-2026-09-15T21-20Z,
author = {TOLL},
title = {scrape on cryptorisk-api.vercel.app},
howpublished = {\url{https://tollindex.com/e/cryptorisk-api-vercel-app-api-scrape-d11cdb/at/2026-09-15T21-20Z}},
year = {2026},
month = {9},
note = {Pinned view of the snapshot of 2026-09-15 21:20 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.