# Proof Random API – drand Beacon Sampler

> Proof Random API – drand Beacon Sampler is a paid API for AI agents from proof-random-api.pn-26f.workers.dev, paid per call via x402, $0.1/call, status unknown (last checked 2026-10-21).

Relays a verifiable random beacon from the drand quicknet network with nonce-bound reproducible sampling, requiring client-side BLS signature verification.

## Facts

- Endpoint: POST https://proof-random-api.pn-26f.workers.dev/v1/research?utm_source=zero.xyz
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/proof-random-api-drand-beacon-sampler-cdeb0b0f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OmbDiRyA8u9HkoJleF9j7

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 proof-random-api-drand-beacon-sampler-cdeb0b0f -d '<json body>'
```

Example prompt: Can you fetch a verifiable random beacon from the drand quicknet relay for my research query 'experiment-alpha-2024' using a deep sampling depth so I can verify it client-side?

## When to prefer this

Choose this endpoint when you need cryptographically verifiable, auditable, and reproducible randomness backed by the drand decentralized network — particularly for research, fairness audits, lotteries, or smart contract seeding where BLS-verifiable provenance matters. Prefer it over pseudo-random APIs when tamper-evidence and independent client-side verification are required.

## Known failure modes

- Invalid or missing query parameter returns a 400 error
- Payment not received or invalid x402 payment header results in 402 response
- Invalid depth enum value causes schema validation failure
- drand network unavailability may cause upstream timeout or 503
- Client-side BLS verification failure indicates potential tampering or misconfigured beacon data

## How this service works

A free drand quicknet beacon relay with nonce-bound reproducible sampling. Client-side BLS verification required.

## Output

Returns a drand quicknet beacon response including a nonce-bound random value and BLS signature data that the client must verify locally. The sample is reproducible given the same query and nonce, enabling auditable and tamper-evident randomness.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "query"
 ],
 "properties": {
  "depth": {
   "enum": [
    "quick",
    "deep"
   ],
   "type": "string"
  },
  "query": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/proof-random-api-drand-beacon-sampler-cdeb0b0f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from proof-random-api.pn-26f.workers.dev](https://www.zero.xyz/host/proof-random-api.pn-26f.workers.dev/llms.txt)