# x402.shizu.me Random Number Generator

> x402.shizu.me Random Number Generator is a paid API for AI agents from x402.shizu.me, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-14).

Returns cryptographically-secure random bytes as hex or a uniform random integer within an inclusive range, each response including a request_id and timestamp for auditability.

## Facts

- Endpoint: GET https://x402.shizu.me/rand
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-shizu-me-random-number-generator-6c9ced04
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_I4tGTtf913FhmWeg4rXAV

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability x402-shizu-me-random-number-generator-6c9ced04
```

Example prompt: Give me a cryptographically secure random integer between 1 and 100 — I need a verifiable receipt with a request ID and timestamp so I can cite it.

## When to prefer this

Prefer this endpoint when the agent needs unbiased, cryptographically-secure entropy with an auditable receipt — not a seeded PRNG — especially when the random output must be cited, logged, or verified later. Ideal for fair draws, nonce generation, or any workflow where tamper-evidence matters.

## Known failure modes

- bytes parameter out of range (must be 1–256): returns error
- min greater than max in integer range request: returns error
- missing required parameters returns descriptive error
- payment failure or insufficient USDC balance blocks the request

## How this service works

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).

## Output

A JSON response containing either a hex string of the requested random bytes (1–256 bytes) or a uniform random integer within the specified inclusive range, accompanied by a request_id and timestamp for audit and citation purposes.

## Request schema (JSON Schema)

```json
{
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "method"
   ],
   "properties": {
    "method": {
     "const": "GET"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "bytes"
     ],
     "properties": {
      "bytes": {
       "type": "string"
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ts": 1784300000,
  "hex": "9f...c1",
  "request_id": "a1b2c3d4e5f6a7b8"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-shizu-me-random-number-generator-6c9ced04/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.shizu.me](https://www.zero.xyz/host/x402.shizu.me/llms.txt)