Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-21 · today

gateway.spraay.app/api/v1/gpu/run

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://gateway.spraay.app/api/v1/gpu/run
Sourcecdp_bazaar
Declared methodPOST
Catalog networkeip155:8453
Receiving address0xad62f03c7514bb8c51f1ea70c2b75c37404695c8
Declared price (base units)60000
Catalog statusactive
First seen / last seen2026-09-05 01:03 UTC / 2026-10-21 13:01 UTC
Catalog-reported calls / payers (30d)3 / 3

2.Probe history

2026-09-052026-10-21
Figure 1. Probe timeline, last 22 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap. Marks closer than one mark width are stepped down one lane.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-10-21 13:40 UTCPOSTpass402460 ms—
2026-10-19 22:40 UTCPOSTpass402221 ms—
2026-10-18 13:40 UTCPOSTpass402195 ms—
2026-10-17 04:40 UTCPOSTpass402276 ms—
2026-10-15 12:40 UTCPOSTpass402179 ms—
2026-10-14 03:40 UTCPOSTpass402197 ms—
2026-10-12 21:40 UTCPOSTpass402179 ms—
2026-10-11 21:40 UTCPOSTpass402261 ms—
2026-10-10 21:40 UTCPOSTpass40297 ms—
2026-10-09 15:40 UTCPOSTpass40290 ms—
2026-10-08 13:40 UTCPOSTpass40287 ms—
2026-10-07 13:40 UTCPOSTpass4022043 ms—
2026-10-06 13:40 UTCPOSTpass402203 ms—
2026-10-05 04:40 UTCPOSTpass40286 ms—
2026-10-04 10:31 UTCPOSTpass402152 ms—
2026-09-28 10:30 UTCPOSTpass402195 ms—
2026-09-23 10:31 UTCPOSTpass402129 ms—
2026-09-19 11:24 UTCPOSTpass402114 ms—
2026-09-17 11:24 UTCPOSTpass402180 ms—
2026-09-13 11:24 UTCPOSTpass402203 ms—
2026-09-09 11:24 UTCPOSTpass402160 ms—
2026-09-05 11:24 UTCPOSTpass402161 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

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.

20–2,000 characters · 0 so far