dataforagents.net/v1/steam/search
1.Catalog declaration
| Resource URL | https://dataforagents.net/v1/steam/search |
| Source | cdp_bazaar |
| Declared method | GET |
| Catalog network | eip155:8453 |
| Receiving address | 0x5d4ecba4458c49b6f92fd5384686f0caf0c3080b |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-09-04 01:03 UTC / 2026-10-21 13:01 UTC |
| Catalog-reported calls / payers (30d) | 7 / 7 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-21 13:40 UTC | GET | pass | 402 | 235 ms | — |
| 2026-10-19 22:40 UTC | GET | pass | 402 | 88 ms | — |
| 2026-10-18 13:40 UTC | GET | pass | 402 | 331 ms | — |
| 2026-10-17 04:40 UTC | GET | pass | 402 | 2118 ms | — |
| 2026-10-15 15:40 UTC | GET | pass | 402 | 43 ms | — |
| 2026-10-14 12:40 UTC | GET | pass | 402 | 296 ms | — |
| 2026-10-12 21:40 UTC | GET | pass | 402 | 171 ms | — |
| 2026-10-11 21:40 UTC | GET | pass | 402 | 180 ms | — |
| 2026-10-10 21:40 UTC | GET | pass | 402 | 340 ms | — |
| 2026-10-09 21:40 UTC | GET | pass | 402 | 314 ms | — |
| 2026-10-08 16:40 UTC | GET | pass | 402 | 168 ms | — |
| 2026-10-07 13:40 UTC | GET | pass | 402 | 102 ms | — |
| 2026-10-06 16:40 UTC | GET | pass | 402 | 48 ms | — |
| 2026-10-05 04:40 UTC | GET | pass | 402 | 73 ms | — |
| 2026-10-04 13:40 UTC | GET | pass | 402 | 74 ms | — |
| 2026-10-03 16:40 UTC | GET | pass | 402 | 559 ms | — |
| 2026-10-02 16:40 UTC | GET | pass | 402 | 79 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 143 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 172 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 78 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 128 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 44 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 89 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 170 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 258 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 179 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 170 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 83 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 159 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 354 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash, and that transaction is the evidence. On this page a receipt means the seller's own settlement receipt (PAYMENT-RESPONSE); a settled row can have none (see “tx from our index”). A settled row reads as nonce-bound when the on-chain re-read matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count. The Stellar re-read checks payer, payee, amount and asset. A row reads as amount + payee when the re-read matched payer, payee, amount and asset and did not bind a one-time value. That tier holds rows from before 2026-09-04 and Stellar rows. They keep the settled label rather than being demoted (methodology). settled is the transfer vet402 confirmed on-chain. delivered is the response arriving. A settled row whose paid request answered 5xx counts as settled and not as delivered. definitions.
Terms in this table
settled (nonce-bound)- vet402 re-read the transfer on-chain in that chain's pinned settlement asset, and the on-chain re-read matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count.
L2 no_declaration- the listing's output schema gave vet402 nothing to check this response against (no schema, a schema with no required keys and no example properties, or example properties with a content type that is not JSON). An output example the seller puts in the 402 (extensions.bazaar.info.output.example) is not checked yet.
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 | On-chain tx | Payment chain | Latency |
|---|---|---|---|---|---|
| 09-28 00:012026-09-28 00:01 UTC | settled (nonce-bound) | 200 | 0x463a633d…d510 | Base | 1079 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | |||||
| 09-21 18:022026-09-21 18:02 UTC | settled (nonce-bound) | 200 | 0x696bc170…646f | Base | 1154 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | |||||
| 09-12 06:012026-09-12 06:01 UTC | settled (nonce-bound) | 200 | 0xf1adba26…7f27 | Base | 989 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | |||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 3 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/eda03652-ca60-47fd-acff-2b97aa1edda9)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.