Independent MeasurementEndpoint record (L0 · L1)Published state: unverifiedLast probed: 2026-09-29 · 1 day ago
pulse-api-production-7aae.up.railway.app/arbitrum/v1/preflight
1.Catalog declaration
| Resource URL | https://pulse-api-production-7aae.up.railway.app/arbitrum/v1/preflight |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:42161 |
| Receiving address | 0xa05b83c9a2228b1f4e32952a71e5b189df4f3973 |
| Declared price (base units) | 200000 |
| Catalog status | active |
| First seen / last seen | 2026-09-27 01:02 UTC / 2026-09-30 01:03 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
2026-09-272026-09-29
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-29 07:38 UTC | POST | unverified | 400 | 116 ms | request_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input). |
| 2026-09-28 10:30 UTC | POST | fail | 400 | 175 ms | no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail. |
| 2026-09-27 10:30 UTC | POST | fail | 400 | 102 ms | no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail. |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
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.