racingpulse.theaslangroupllc.com/api/going
1.Catalog declaration
| Resource URL | https://racingpulse.theaslangroupllc.com/api/going |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x50ab2018c06c6e4eaa9ba52057eb55ed284912fc |
| Declared price (base units) | 20000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:02 UTC |
| Catalog-reported calls / payers (30d) | 4 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-29 04:40 UTC | GET | pass | 402 | 461 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 180 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 135 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 249 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 2236 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 305 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 1058 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 1452 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 139 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 138 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 171 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 148 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 222 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 283 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 330 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 72 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 262 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 324 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 2097 ms | — |
| 2026-09-15 13:40 UTC | GET | pass | 402 | 540 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 136 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 70 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 2214 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 424 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 499 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 118 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 91 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 249 ms | — |
| 2026-09-09 23:40 UTC | GET | pass | 402 | 97 ms | — |
| 2026-09-09 14:40 UTC | GET | pass | 402 | 73 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled with a receipt, and 1 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. A settled row reads as nonce-bound when the on-chain re-read also matched the one-time signature nonce we generated for that purchase, and amount + payee when it matched amount, payee, asset and chain with no nonce on record — the binding shipped on 2026-09-04, so earlier rows carry the weaker evidence and keep their label rather than being demoted (methodology). settled is the transfer we confirmed on-chain; delivered is the response arriving. A settled row whose paid request answered 5xx counts as settled and not as delivered — definitions.
A row marked tx from our index came back with no settlement receipt from the seller. Our own index of on-chain settlements found the transfer afterwards — our payer, this endpoint's payee, the exact amount, inside the time window — and the row goes through the same on-chain re-read as any other before it reads settled. The seller did not name that transaction; we did (methodology).
Terms in this table
settled (nonce-bound)- vet402 confirmed the USDC transfer on-chain, and the on-chain re-read also matched the one-time nonce vet402 signed for that purchase.
settled (amount + payee)- vet402 confirmed the USDC transfer on-chain; the on-chain re-read matched amount, payee, asset and chain; no nonce was on record (rows before 2026-09-04).
L2 not_checked- not checked: the paid request did not answer 200, so there was no response to check against the listing's output schema.
L2 no_declaration- the listing declares no output schema to check the response against.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “under re-check”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-16 18:002026-09-16 18:00 UTC | settled (nonce-bound)tx from our index | — | 0x65d3370f…f492 | 20155 ms |
| 20000 units (≈ $0.02 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
| 09-10 12:082026-09-10 12:08 UTC | settled (nonce-bound) | 200 | 0xb94543a1…d8d5 | 1772 ms |
| 20000 units (≈ $0.02 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-02 19:012026-09-02 19:01 UTC | settled (amount + payee)tx from our index | — | 0xe8baa51b…79e8 | 20212 ms |
| 20000 units (≈ $0.02 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 1 delivered and updates as the record grows. It carries the host it is about and the date it was last measured, so a saved copy cannot pass itself off as current. It states a measurement, not a rating.
[](https://vet402.com/observatory/e/1cc23084-5e78-4490-a453-c1c7418cb75d)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.
About the purchase at 2026-09-02T19:01:20Z (UTC). The form starts with that time; add what you saw instead.