Skip to main content
vet402
MenuClose
Independent MeasurementEndpoint record (L0 · L1)Published state: unverifiedLast probed: 2026-11-12 · today
vet402Back to the registerMethodology

money-reactor.makar52nn2016.workers.dev/api/weather

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://money-reactor.makar52nn2016.workers.dev/api/weather
Sourcecdp_bazaar
Declared methodGET
Catalog networkeip155:8453
Receiving address0xf47b7e5912fd4218ac4c992cdc6fae04e1ff512e
Declared price (base units)2000
Catalog statusactive
First seen / last seen2026-10-20 13:01 UTC / 2026-11-12 18:05 UTC
Catalog-reported calls / payers (30d)8 / 4

2.Probe history

2026-10-212026-11-12
Figure 1. Probe timeline, last 12 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-11-12 16:40 UTCGETfail402114 msprice_mismatchDeclared 2000 of 0x8335…2913; the 402 offered 10000 of 0x8335…2913.
2026-11-10 13:40 UTCGETunverified429142 msrate_limitedThe endpoint answered 429; a rate limit is not a verdict on the payment wall.
2026-11-08 13:40 UTCGETfail40269 msmetadata_mismatchDeclared payTo 0xf47b…512e on eip155:8453; the 402 offered 0x9639…59b4 on eip155:8453.
2026-11-06 04:40 UTCGETpass40279 ms—
2026-11-03 21:40 UTCGETunverified429355 msrate_limitedThe endpoint answered 429; a rate limit is not a verdict on the payment wall.
2026-10-31 22:40 UTCGETpass402126 ms—
2026-10-29 22:40 UTCGETpass402120 ms—
2026-10-28 04:40 UTCGETpass40231 ms—
2026-10-26 15:40 UTCGETpass402117 ms—
2026-10-24 16:47 UTCGETpass402138 ms—
2026-10-22 10:30 UTCGETfail402104 msprice_mismatchDeclared 2000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-10-21 10:30 UTCGETfail40299 msprice_mismatchDeclared 2000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.

3.L1 — real purchases

No paid purchases recorded for this endpoint yet.

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint. We first send one confirmation email; nothing else goes out until you confirm.

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

A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.

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. A dispute filed on the record form puts an active listing on a priority list. L0 runs probe that list before their ordinary queue, one run at a time. A listing whose URL has an unfilled path parameter is not put on that list. One run measures up to 50 priority listings, at most 5 from one site. Published fails whose catalog declaration changed, or that rest on probes recorded under earlier rules, take places first, and disputes fill the places left. A listing probed in the past 60 minutes waits for a later run. A dispute that no run reaches within 7 days leaves the list. The scheduled L0 run is at 10:30 UTC, and an L0 run at another time can measure the listing first. The record stays on this page. When a run measures the listing, the new probe is added to its history. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.

About the purchase at 2026-11-08T03:31:53Z (UTC). The form starts with that time; add what you saw instead.

20–2,000 characters · 59 so far