x402.freeq.one/tools/verify_worldid
1.Catalog declaration
| Resource URL | https://x402.freeq.one/tools/verify_worldid |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x90b0dc893406d6ea63bb077ed59f5e8340f98d84 |
| Declared price (base units) | 5000 |
| Catalog status | active |
| First seen / last seen | 2026-08-23 01:18 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 45 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 04:40 UTC | POST | pass | 402 | 359 ms | — |
| 2026-10-18 13:40 UTC | POST | pass | 402 | 349 ms | — |
| 2026-10-17 04:40 UTC | POST | pass | 402 | 1628 ms | — |
| 2026-10-15 15:40 UTC | POST | pass | 402 | 166 ms | — |
| 2026-10-14 12:40 UTC | POST | pass | 402 | 468 ms | — |
| 2026-10-12 21:40 UTC | POST | pass | 402 | 253 ms | — |
| 2026-10-11 21:40 UTC | POST | pass | 402 | 1726 ms | — |
| 2026-10-10 21:40 UTC | POST | pass | 402 | 316 ms | — |
| 2026-10-09 21:40 UTC | POST | pass | 402 | 126 ms | — |
| 2026-10-08 16:40 UTC | POST | pass | 402 | 153 ms | — |
| 2026-10-07 16:40 UTC | POST | pass | 402 | 103 ms | — |
| 2026-10-06 16:40 UTC | POST | pass | 402 | 138 ms | — |
| 2026-10-05 04:40 UTC | POST | pass | 402 | 108 ms | — |
| 2026-10-04 13:40 UTC | POST | pass | 402 | 216 ms | — |
| 2026-10-03 16:40 UTC | POST | pass | 402 | 140 ms | — |
| 2026-10-02 22:40 UTC | POST | pass | 402 | 123 ms | — |
| 2026-10-01 22:40 UTC | POST | pass | 402 | 130 ms | — |
| 2026-10-01 04:40 UTC | POST | pass | 402 | 337 ms | — |
| 2026-09-30 13:40 UTC | POST | pass | 402 | 271 ms | — |
| 2026-09-29 16:40 UTC | POST | pass | 402 | 189 ms | — |
| 2026-09-28 22:40 UTC | POST | pass | 402 | 110 ms | — |
| 2026-09-28 04:40 UTC | POST | pass | 402 | 104 ms | — |
| 2026-09-27 13:40 UTC | POST | pass | 402 | 115 ms | — |
| 2026-09-26 16:40 UTC | POST | pass | 402 | 231 ms | — |
| 2026-09-25 22:40 UTC | POST | pass | 402 | 2099 ms | — |
| 2026-09-25 04:40 UTC | POST | pass | 402 | 143 ms | — |
| 2026-09-24 13:40 UTC | POST | pass | 402 | 134 ms | — |
| 2026-09-23 16:40 UTC | POST | pass | 402 | 232 ms | — |
| 2026-09-23 04:40 UTC | POST | pass | 402 | 480 ms | — |
| 2026-09-21 22:40 UTC | POST | pass | 402 | 165 ms | — |
3.L1 — real purchases
1 of 1 paid attempts settled on-chain, and 1 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash, and that transaction is the evidence. On this page a receipt means the seller's own settlement receipt (PAYMENT-RESPONSE); a settled row can have none (see “tx from our index”). A settled row reads as nonce-bound when the on-chain re-read also matched the one-time signature nonce we generated for that purchase, and amount + payee when it matched amount, payee, asset and chain with no nonce on record — the binding shipped on 2026-09-04, so earlier rows carry the weaker evidence and keep their label rather than being demoted (methodology). settled is the transfer we confirmed on-chain; delivered is the response arriving. A settled row whose paid request answered 5xx counts as settled and not as delivered — definitions.
A row marked tx from our index came back with no settlement receipt from the seller. Our own index of on-chain settlements found the transfer afterwards — our payer, this endpoint's payee, the exact amount, inside the time window — and the row goes through the same on-chain re-read as any other before it reads settled. The seller did not name that transaction; we did (methodology).
Terms in this table
settled (nonce-bound)- vet402 confirmed the USDC transfer on-chain, and the on-chain re-read also matched the one-time nonce vet402 signed for that purchase.
L2 no_declaration- the listing declares no output schema to check the response against.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “under re-check”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Latency |
|---|---|---|---|---|
| 09-22 00:012026-09-22 00:01 UTC | settled (nonce-bound)tx from our index | 200 | 0x116a1615…8eb7 | 4794 ms |
| 5000 units (≈ $0.005 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 delivered and updates as the record grows. It carries the host it is about and the date it was last measured, so a saved copy cannot pass itself off as current. It states a measurement, not a rating.
[](https://vet402.com/observatory/e/c9dfd2db-3723-42d8-ad7b-e8d761d4cc02)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-23 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-22 | delisted | {"status":"active"} | {"status":"delisted"} |
unverified is not a failure; a fail is published only after two consecutive failing probes. Definitions: methodology.
5.Dispute this record
Think a measurement above is wrong? Say which probe or purchase and what you observed instead. One person reads it and replies. The record is never deleted on dispute: if it was wrong, the correction is published with the same weight; if it was right, it stands. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference), which re-measures through the normal publication gate.