techforce-agents.onrender.com/api/amazon-products
1.Catalog declaration
| Resource URL | https://techforce-agents.onrender.com/api/amazon-products |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x2f6ba59f09fd4693c6df12aec5acf14a4ba43f1d |
| Declared price (base units) | 30000 |
| Catalog status | delisted (since 2026-09-28 23:00 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-28 01:02 UTC |
| Catalog-reported calls / payers (30d) | 3 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 13:40 UTC | GET | fail | 503 | 191 ms | no_402HTTP 503 instead of 402 to an unpaid GET. |
| 2026-09-27 16:40 UTC | GET | fail | 503 | 300 ms | no_402HTTP 503 instead of 402 to an unpaid GET. |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 297 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 445 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 1752 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 321 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 247 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 272 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 136 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 109 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 161 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 106 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 155 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 339 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 384 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 357 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 403 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 295 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 252 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 318 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 187 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 105 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 372 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 380 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 250 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 308 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 125 ms | — |
| 2026-09-09 23:40 UTC | GET | pass | 402 | 414 ms | — |
| 2026-09-09 14:40 UTC | GET | pass | 402 | 121 ms | — |
| 2026-09-08 17:40 UTC | GET | fail | 400 | 160 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
3.L1 — real purchases
1 of 1 paid attempts settled on-chain, and 1 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 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.
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.
L2 match- the response had the fields the listing's output schema declares.
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 | Latency |
|---|---|---|---|---|
| 09-05 07:012026-09-05 07:01 UTC | settled (nonce-bound) | 200 | 0x2aa98a1c…22e6 | 15244 ms |
| 30000 units (≈ $0.03 USDC) · L2 matchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 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/4b0328e0-3c46-4550-9813-f8ac1e51d03c)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-28 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-09-02 | relisted | {"status":"delisted"} | {"status":"active"} |
| 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.