Random
by DEX Data & Agent Utilities in Onchain & crypto
Cryptographically secure randomness for agents that are deterministic or sandboxed. Two modes: raw bytes (?bytes=1..1024, default 32, clamped) returning hex and base64url; or uniform integers (?min= and ?max= together, optional ?count=1..1000) rejection-sampled so there is no modulo bias. Errors: 400 bad_bytes for a non-integer, bad_range when max is not greater than min, range_too_large. Generated server-side, and the response says so - if nobody may have seen it, generate it yourself.
https://x402.donnyautomation.com/random- Price
- $0.01
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 6 h ago, next in 3 days
Reliability
Latest check failed 6 h ago: Served content without asking for payment
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://x402.donnyautomation.com/random
Each call costs $0.01 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
GET https://x402.donnyautomation.com/random?bytes=32Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
bytes | string | No | Random bytes to return, 1..1024 (default 32). Returned as hex and base64url. |
count | string | No | How many integers, 1..1000 (default 1). Integer mode only. |
max | string | No | Upper bound (inclusive) for integer mode. Must be greater than min. |
min | string | No | With max: return uniform integers in [min, max] inclusive instead of bytes. |
Example response
The provider's example. We can't check it without paying.
{
"base64": "n4bQgYhMfWWa…",
"bytes": 32,
"hex": "9f86d081884c7d65…",
"source": "node:crypto randomBytes (CSPRNG)",
"ts": "2026-08-01T00:00:00.000Z"
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.01.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://x402.donnyautomation.com/random?bytes=32'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://x402.donnyautomation.com/random?bytes=32' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fx402.donnyautomation.com%2Frandom
const res = await pay("https://x402.donnyautomation.com/random?bytes=32");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://x402.donnyautomation.com/random?bytes=32")
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 6 h ago | Served content without asking for payment | 200 | 467 ms | - |
| 3 days ago | Served content without asking for payment | 200 | 485 ms | - |
| 3 days ago | Served content without asking for payment | 200 | 460 ms | - |
| 4 days ago | Served content without asking for payment | 200 | 509 ms | - |
| 4 days ago | Served content without asking for payment | 200 | 487 ms | - |
Show 10 older checks
| 4 days ago | Served content without asking for payment | 200 | 211 ms | - |
| 4 days ago | Served content without asking for payment | 200 | 494 ms | - |
| 4 days ago | Served content without asking for payment | 200 | 364 ms | - |
| 5 days ago | Served content without asking for payment | 200 | 208 ms | - |
| 5 days ago | Served content without asking for payment | 200 | 212 ms | - |
| 5 days ago | Served content without asking for payment | 200 | 484 ms | - |
| 5 days ago | Served content without asking for payment | 200 | 482 ms | - |
| 5 days ago | Served content without asking for payment | 200 | 512 ms | - |
| 6 days ago | Served content without asking for payment | 200 | 617 ms | - |
| 6 days ago | Served content without asking for payment | 200 | 498 ms | - |