# Provably Fair Draw Verifier

> Provably Fair Draw Verifier is a paid API for AI agents from pyfile-agent.taile3ff35.ts.net:10000, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-13).

Recomputes a provably-fair random draw and verifies that sha256(server_seed) matches the original commit, confirming the result was not manipulated.

## Facts

- Endpoint: GET https://pyfile-agent.taile3ff35.ts.net:10000/data/fair/verify
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/provably-fair-draw-verifier-ce9560b4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_i2vM-kpNYLU6BlTkOhb52

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 provably-fair-draw-verifier-ce9560b4
```

Example prompt: Can you verify that round 42 of the lottery was fair? The client seed is 'myseed123', nonce is 7, and the draw range was 1 to 100 — I want to confirm the server seed's sha256 matches the original commit.

## When to prefer this

Use this endpoint when you need to cryptographically audit a provably fair random draw and confirm the house did not manipulate the outcome. It is the correct choice when you have a round number, client seed, nonce, and numeric range and want an independent recomputation that checks the sha256(server_seed) == commit invariant. Prefer this over manual hash computation or trusting the platform's own display.

## Known failure modes

- Missing required query parameters (round, client_seed, nonce, min, max) result in an error response
- Invalid round number returns no matching draw data
- Mismatched sha256 hash indicates a tampered or incorrect server seed — not an API error but a negative verification result
- min >= max or invalid range values may return a validation error
- Network or payment failure returns HTTP 402 or 5xx

## How this service works

Recompute a draw and check sha256(server_seed)==commit. ?round=1&client_seed=s&nonce=1&min=1&max=100

## Output

Returns the recomputed draw result along with the sha256 hash of the server seed and a boolean or status indicating whether that hash matches the original commit — confirming or refuting that the random outcome was pre-committed and untampered.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/provably-fair-draw-verifier-ce9560b4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from pyfile-agent.taile3ff35.ts.net:10000](https://www.zero.xyz/host/pyfile-agent.taile3ff35.ts.net%3A10000/llms.txt)