crypto random bytes derived
fittings.shRandomnessderived
GET https://fittings.sh/v1/crypto/random-bytes
passabsent from every registry#1 by calls of 9 on this host
0.0031 USDC
per call, as the listing declares it on eip155:
Compare with anotherEvery figure as JSONCite this page
the price, as of 2026-09-14 12:43 UTC · method
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 2
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-08-15 20:59 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.0031 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 24 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.
TOLL files crypto random bytes under randomness: a GET endpoint on fittings.sh, listed in neither registry at the last pull.
A call to crypto random bytes costs 0.0031 USDC on Base, as declared.
The listing describes the request as the query parameters bytes and encoding.
crypto random bytes answered the sweep of 2026-09-14 with a valid 402, as at every sweep since 2026-09-11.
fittings.sh lists 9 endpoints; crypto random bytes is tied 1st by calls with 2 others.
Of the calls counted across fittings.sh, crypto random bytes takes 18%.
Over 30 days: 2 calls, one payer.
The most recent call was 31 days before the snapshot.
crypto random bytes sits nearest in price to json repair (agent-data-fixer-production.up.railway.app) and fair commit (pyfile-agent.taile3ff35.ts.net) among listings in randomness.
crypto random bytes is priced above 62% of comparable listings in randomness.
Its payee wallet receives for 145 listed endpoints on one host.
Seller tags: crypto.
The listing for crypto random bytes fails only advisory checks about output metadata; the verdict is unaffected.
crypto random bytes was missing from the Coinbase registry at the pull of 2026-09-14, confirmed at the pull of 2026-09-15; that is registry presence, not liveness.
Where the sentences above compare this endpoint with others, the comparison is against the index as it stands now, live; the figures above are final.
the payment options, as of 2026-09-14 12:43 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.0031 USDC | upto | 0xe02544…d98638 |
the checks, as of 2026-09-14 05:24 UTC · methodendpoint 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-09-14 05:24 UTC | pass | 1 | daily-2026-09-14 |
| 2026-09-13 05:19 UTC | pass | 1 | daily-2026-09-13 |
| 2026-09-12 07:35 UTC | pass | 1 | daily-2026-09-12 |
| 2026-09-11 11:23 UTC | pass | 1 | daily-2026-09-11 |
Presence in a registry, not liveness of the service (method). Newest first.
- 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-08-15 20:59 UTC · method
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"bytes": 32,
"encoding": "hex"
}
},
"output": null
}Cite this page
This endpoint is delisted: the page is frozen at its last observation and its live URL is the stable one. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "crypto random bytes on fittings.sh". https://tollindex.com/e/fittings-sh-v1-crypto-random-bytes-91c23a. Accessed [access date].
BibTeX
@misc{toll-e-fittings-sh-v1-crypto-random-bytes-91c23a-2026-09-15,
author = {TOLL},
title = {crypto random bytes on fittings.sh},
howpublished = {\url{https://tollindex.com/e/fittings-sh-v1-crypto-random-bytes-91c23a}},
year = {2026},
month = {9},
note = {Frozen at its last observation, 2026-09-15 21:20 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.