Cryptographically-secure randomness with a receipt
Cryptographically-secure randomness with a receipt. GET ?bytes= returns hex (1-256 bytes); add ?min=&max= for a uniform integer in an inclusive range. Each response carries a request_id and timestamp — unbiased entropy an agent can cite to a counterparty, not a seeded PRNG. Need provable fairness over time? /rand/commit does commit-reveal (commitment now, value later).
Answeringour last check, 2026-09-24
1 of 1checks answered this week
1246 msmedian answer time
$0.003listed price per call
$0.003price it asked us
Paid test badge: not yet. The checks above are free: we call the tool without paying and read the payment request it sends back. The Verified badge needs paid calls whose answers match the promised output, and nobody can buy a badge.
Endpoint
GET https://x402.shizu.me/rand
| Category | Everything else |
|---|---|
| Provider host | x402.shizu.me |
| Networks | eip155:8453 |
| Payment schemes | exact |
| Self-reported calls, 30 days | 11 from 7 payers (the provider's figure, not ours) |
Our checks, last 30 days
| Day | Result | HTTP | Asked | Time |
|---|---|---|---|---|
| 2026-09-24 | valid payment request | 402 | $0.003 | 1246 ms |
Example input (from the provider)
{
"method": "GET",
"queryParams": {
"bytes": "16"
},
"type": "http"
}
Promised output schema (from the provider)
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"input": {
"properties": {
"method": {
"const": "GET"
},
"queryParams": {
"properties": {
"bytes": {
"type": "string"
}
},
"required": [
"bytes"
],
"type": "object"
}
},
"required": [
"method"
],
"type": "object"
}
}
}