Skip to main content
vet402
Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-09-20 · 6 days ago
vet402Back to the registerMethodology

geolithicintelligence.com/api/claim

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://geolithicintelligence.com/api/claim
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0x54e26771267a0b774341882272e953cc833a2fe0
Declared price (base units)1000000
Catalog statusdelisted (since 2026-09-21 01:03 UTC)
First seen / last seen2026-09-10 01:03 UTC / 2026-09-20 01:03 UTC
Catalog-reported calls / payers (30d)3 / 1

2.Probe history

2026-09-102026-09-20
Figure 1. Probe timeline, last 16 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-20 13:40 UTCGETfail50371 msno_402
2026-09-19 16:40 UTCGETfail50364 msno_402
2026-09-18 22:40 UTCGETfail40234 msprice_mismatch
2026-09-18 04:40 UTCGETfail—9999 mstimeout
2026-09-17 13:40 UTCGETfail402884 msprice_mismatch
2026-09-16 22:40 UTCGETfail402142 msprice_mismatch
2026-09-15 22:40 UTCGETfail40265 msprice_mismatch
2026-09-15 04:40 UTCGETfail402256 msprice_mismatch
2026-09-14 16:40 UTCGETfail40266 msprice_mismatch
2026-09-13 22:40 UTCGETfail40252 msprice_mismatch
2026-09-13 13:40 UTCGETfail4022187 msprice_mismatch
2026-09-12 22:40 UTCGETfail402187 msprice_mismatch
2026-09-12 04:40 UTCGETfail40262 msprice_mismatch
2026-09-11 16:40 UTCGETfail402175 msprice_mismatch
2026-09-11 04:40 UTCGETfail402244 msprice_mismatch
2026-09-10 11:24 UTCGETfail—10000 mstimeout

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.

4.Catalog listing events

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-09-21delisted{"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.