x402.fairseal.io
https://x402.fairseal.io/v1/rng/latestShares a payout wallet with 5 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.
Verifiable random numbers with cryptographic epoch references. Wesolowski 2048-bit VDF epoch chain with on-chain MerkleAnchor reference. For unbiased randomness: POST /v1/rng/commit (free), then GET the reveal_url returned in the response. Do not construct reveal paths yourself.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
33.3% avgResponse time
p50 120ms · p95 403msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 10/1/2026, 3:00:00 PM | 0% | 1 | — |
| 10/2/2026, 3:00:00 PM | 0% | 1 | — |
| 10/3/2026, 3:00:00 PM | 0% | 1 | — |
| 10/4/2026, 4:00:00 PM | 0% | 1 | — |
| 10/5/2026, 4:00:00 PM | 0% | 1 | — |
| 10/6/2026, 5:00:00 PM | 0% | 1 | — |
| 10/7/2026, 7:00:00 PM | 100% | 1 | 434ms |
| 10/7/2026, 9:00:00 PM | 100% | 1 | 120ms |
| 10/7/2026, 10:00:00 PM | 100% | 1 | 120ms |
- Availability
- 9
- Latency
- 100
- Security
- 100
- Transparency
- 67
- Activity
- 4
How often it was reachable when we probed it (weight 35%).
How quickly it answers when it is up — fast scores high (weight 20%).
Whether it serves over working TLS / https (weight 15%).
Whether the operator disclosed what it does — description, schema, identity (weight 15%).
Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).
Confidence 64% — how much probe evidence backs this score. A thin history is flagged, not hidden.
See the scoring methodology for exactly how each number is computed.
Payment
- Currencies
- USDC
- Networks
- base
- Facilitator
- unknown
- SDK
- x402-express
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- —
- Domain registered
- —
- Hosting network
- HETZNER
- Hosting country
- FI
Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.
On-chain activity (base)
Payments per day
last payment 10/7/2026Data table
| Day | Payments | Volume (USD) | Paying wallets |
|---|---|---|---|
| 9/8/2026 | 1 | 0.01 | 1 |
| 9/9/2026 | 16 | 0.07 | 1 |
| 9/10/2026 | 1 | 0 | 1 |
| 9/11/2026 | 2 | 0.03 | 2 |
| 9/12/2026 | 2 | 0 | 1 |
| 9/13/2026 | 2 | 0 | 1 |
| 9/14/2026 | 1 | 0.01 | 1 |
| 9/15/2026 | 2 | 0.04 | 1 |
| 9/16/2026 | 1 | 0.02 | 1 |
| 9/17/2026 | 2 | 0.01 | 2 |
| 9/26/2026 | 2 | 0.04 | 2 |
| 9/27/2026 | 1 | 0.02 | 1 |
| 9/29/2026 | 1 | 0.02 | 1 |
| 9/30/2026 | 3 | 0.02 | 1 |
| 10/3/2026 | 20 | 0.09 | 2 |
| 10/6/2026 | 1 | 0 | 1 |
| 10/7/2026 | 24 | 0.85 | 2 |
Payout address changed 1 time, last on 8/21/2026
- 0x6323…10dC → 0xBd5e…ce28 (base) · 8/21/2026
A changed payout address is worth a second look — it can be routine, but it is also how a hijacked listing redirects funds.
This payout wallet is shared: figures cover all 6 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.
Response schema
{
"$ref": "#/components/schemas/RNGResponse"
}