Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-13 · 7 days ago

modelprices.xyz/llm/context-windows

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://modelprices.xyz/llm/context-windows
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0x63a20fa244d3e6a8902121e99704b7f857dc6ebb
Declared price (base units)10000
Catalog statusactive
First seen / last seen2026-08-30 01:02 UTC / 2026-10-20 01:01 UTC
Catalog-reported calls / payers (30d)2 / 2

2.Probe history

2026-09-042026-10-13
Figure 1. Probe timeline, last 8 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-10-13 10:30 UTCGETpass402135 ms—
2026-09-27 10:31 UTCGETpass402419 ms—
2026-09-23 10:30 UTCGETpass402455 ms—
2026-09-19 11:24 UTCGETpass402171 ms—
2026-09-17 11:24 UTCGETpass402491 ms—
2026-09-12 11:24 UTCGETpass402176 ms—
2026-09-09 11:24 UTCGETpass402169 ms—
2026-09-04 11:24 UTCGETpass402258 ms—

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

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-10-06relisted{"status":"delisted"}{"status":"active"}
2026-10-03delisted{"status":"active"}{"status":"delisted"}
2026-09-29relisted{"status":"delisted"}{"status":"active"}
2026-09-28delisted{"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.

20–2,000 characters · 0 so far