# Provably-Fair Round Commit Hash Lookup

> Provably-Fair Round Commit Hash Lookup 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).

Returns the SHA-256 hash of the server seed committed before a draw for a given round, enabling provable fairness verification

## Facts

- Endpoint: GET https://pyfile-agent.taile3ff35.ts.net:10000/data/fair/commit
- 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-round-commit-hash-lookup-dfb214a9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KZu5w3LLyRYmwSyjz1NUI

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-round-commit-hash-lookup-dfb214a9
```

Example prompt: Can you fetch the provably-fair server seed commitment hash for round 101 so I can verify the draw wasn't manipulated?

## When to prefer this

Use this endpoint when you need to cryptographically verify the fairness of a specific random draw round by retrieving its pre-committed server seed hash. Ideal for auditing lottery, raffle, or gaming outcomes where provable fairness via commit-reveal schemes is required.

## Known failure modes

- Round ID not found or not yet committed — returns an error or empty response
- Missing or invalid round query parameter — may return a bad request error
- Round ID is in the future and no commit exists yet — returns not found
- Service unavailable or network timeout on the Tailscale node

## How this service works

Provably-fair round commit: sha256(server_seed) before any draw. ?round=<id>

## Output

Returns the SHA-256 hash of the server seed that was committed before the draw for the specified round ID, allowing anyone to verify post-reveal that the server seed matches the pre-committed hash and the outcome was not manipulated.

## 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-round-commit-hash-lookup-dfb214a9/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)