https://hubvibe-io.com

What the402 says

Evidence

Statement history

Every statement the402 has made about this endpoint, newest first.

Paid probes

the402 pays for no probes. Every one of these was funded by this endpoint's own claimant, by a buyer verifying it, or from the dispute pool — and it only runs for an endpoint whose operator claimed it and opted in. Requests are published in full; responses as a hash and a redacted excerpt, with whether the answer passed.

Chain activity

Risk flags

{
  "window_days": 30,
  "basis": "ratios over transfers indexed to watched payTos",
  "raise_ratio": 0.8,
  "keep_ratio": 0.7,
  "pairs": [
    {
      "payer": "0x104fea79f30b4fb4da86b6d65951217f914bdd35",
      "pair_txns": 49,
      "payer_ratio": 1,
      "payee_ratio": 0.89
    }
  ]
}

Disputes

Advertised resources

Is this your endpoint?

Claiming it proves you control it — through your own origin, your DNS, or the key you are paid at — and turns on the settings only an operator should have: opting into paid probes you fund, the sandbox, and contesting anything here you think is wrong. How claiming works →

Bought from this endpoint and want the outcome on the record? A signed attestation naming the payment transaction is evidence the402 weighs. How to report an outcome →

● Live Claiming and attestation intake are open on the402's public trust API. What a fixture snapshot renders is a record; the switches it describes are production's.