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

srv1553682.hstgr.cloud/nlp/api/summarize

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://srv1553682.hstgr.cloud/nlp/api/summarize
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0xd32714cc95753d5cd50f56570e98c9d87e7c6dfe
Declared price (base units)3500
Catalog statusactive
First seen / last seen2026-08-16 01:07 UTC / 2026-09-13 01:03 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-09-012026-09-12
Figure 1. Probe timeline, last 4 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-12 11:24 UTCPOSTpass402336 ms—
2026-09-08 11:24 UTCPOSTfail402428 msprice_mismatch
2026-09-04 11:24 UTCPOSTfail402369 msprice_mismatch
2026-09-01 23:14 UTCPOSTfail402342 msprice_mismatch

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

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.