x402.forgemesh.io/endpoint-of-the-day
1.Catalog declaration
| Resource URL | https://x402.forgemesh.io/endpoint-of-the-day |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x84a1827f1705c257e80771fdc2b152aea4a57a08 |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 4 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 04:40 UTC | POST | pass | 402 | 243 ms | — |
| 2026-10-18 16:40 UTC | POST | pass | 402 | 279 ms | — |
| 2026-10-17 04:40 UTC | POST | pass | 402 | 315 ms | — |
| 2026-10-15 15:40 UTC | POST | pass | 402 | 238 ms | — |
| 2026-10-14 12:40 UTC | POST | pass | 402 | 276 ms | — |
| 2026-10-13 03:40 UTC | POST | pass | 402 | 4261 ms | — |
| 2026-10-11 21:40 UTC | POST | pass | 402 | 512 ms | — |
| 2026-10-10 21:40 UTC | POST | pass | 402 | 370 ms | — |
| 2026-10-09 21:40 UTC | POST | pass | 402 | 51 ms | — |
| 2026-10-08 16:40 UTC | POST | pass | 402 | 378 ms | — |
| 2026-10-07 16:40 UTC | POST | pass | 402 | 37 ms | — |
| 2026-10-06 16:40 UTC | POST | pass | 402 | 183 ms | — |
| 2026-10-05 22:40 UTC | POST | pass | 402 | 75 ms | — |
| 2026-10-04 13:40 UTC | POST | pass | 402 | 56 ms | — |
| 2026-10-03 16:40 UTC | POST | pass | 402 | 2044 ms | — |
| 2026-10-02 22:40 UTC | POST | pass | 402 | 100 ms | — |
| 2026-10-01 22:40 UTC | POST | pass | 402 | 63 ms | — |
| 2026-10-01 04:40 UTC | POST | pass | 402 | 457 ms | — |
| 2026-09-30 13:40 UTC | POST | pass | 402 | 824 ms | — |
| 2026-09-29 16:40 UTC | POST | pass | 402 | 499 ms | — |
| 2026-09-28 22:40 UTC | POST | pass | 402 | 384 ms | — |
| 2026-09-28 04:40 UTC | POST | pass | 402 | 509 ms | — |
| 2026-09-27 13:40 UTC | POST | pass | 402 | 157 ms | — |
| 2026-09-26 22:40 UTC | POST | pass | 402 | 226 ms | — |
| 2026-09-26 04:40 UTC | POST | pass | 402 | 111 ms | — |
| 2026-09-25 13:40 UTC | POST | pass | 402 | 134 ms | — |
| 2026-09-24 16:40 UTC | POST | pass | 402 | 320 ms | — |
| 2026-09-23 22:40 UTC | POST | pass | 402 | 286 ms | — |
| 2026-09-23 04:40 UTC | POST | pass | 402 | 364 ms | — |
| 2026-09-22 13:40 UTC | POST | pass | 402 | 172 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.
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-09 07:012026-09-09 07:01 UTC | settled (nonce-bound) | 200 | 0x4723b04a…d6d1 | 815 ms |
| 1000 units (≈ $0.001 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/0dadd27a-e767-4c90-be63-3647336cb1e8)4.Catalog listing events
No listing changes observed.
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.