x402.fairseal.io

https://x402.fairseal.io/v1/rng/latest

Shares a payout wallet with 1 other endpoint — its adoption is attributed from that shared wallet's traffic, not earned exclusively.

Cryptographically verifiable random number. VDF-proven entropy (Wesolowski 2048-bit), pool-served sub-2ms latency.

60
reliability

Reliability & health

Uptime and response time from our own unpaid probes, plus the reliability score built from them.

7 days 30 days

Uptime

100.0% avg
0% 50% 100% Aug 19Aug 20Aug 21Aug 22

Response time

p50 406ms · p95 492ms
0ms 400ms 800ms Aug 19Aug 20Aug 21Aug 22
Data table
Reliability history per time bucket over the last 30 days (daily).
Bucket Uptime Probes Response time
8/19/2026, 12:00:00 AM 100% 13 402ms
8/20/2026, 12:00:00 AM 100% 21 410ms
8/21/2026, 12:00:00 AM 100% 22 406ms
8/22/2026, 12:00:00 AM 100% 3 777ms
60
Composite reliability — the weighted average of the dimensions below, on a 0–100 scale.
Availability
100

How often it was reachable when we probed it (weight 35%).

Latency
96

How quickly it answers when it is up — fast scores high (weight 20%).

Security
100

Whether it serves over working TLS / https (weight 15%).

Transparency
67

Whether the operator disclosed what it does — description, schema, identity (weight 15%).

Activity
4

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 100% — 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)

16
payments (30d)
0.07
USD volume (30d)
2
paying wallets (30d)

Payments per day

last payment 8/21/2026
0 3 6 Aug 1Aug 2Aug 20Aug 21
Data table
Settled payments per day.
Day Payments Volume (USD) Paying wallets
8/1/2026 3 0 1
8/2/2026 1 0 1
8/19/2026 6 0.01 1
8/20/2026 2 0.01 2
8/21/2026 4 0.05 1

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 2 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"
}