Independent MeasurementEndpoint record (L0 · L1)Published state: unverifiedLast probed: 2026-08-20 · 40 days ago
tokensqueezer-production.up.railway.app/compress
1.Catalog declaration
| Resource URL | https://tokensqueezer-production.up.railway.app/compress |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x8e57bfde053dbb6862991759c19affc5f383d5d0 |
| Declared price (base units) | 2000 |
| Catalog status | delisted (since 2026-08-27 01:15 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-08-26 01:39 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
2026-08-20
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-08-20 10:50 UTC | POST | fail | 402 | 133 ms | accepts_invalidRecorded before the 2026-09-29 change, when the probe read only the first 4,000 bytes of the 402 body; this body began like an x402 envelope, so the fail may be vet402's measuring error rather than the seller's. |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-08-27 | delisted | {"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.