Skip to main content
vet402
Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-09-26 · 5 days ago
vet402Back to the registerMethodology

api.robotsshop.io/v0/search

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://api.robotsshop.io/v0/search
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0x53831fab63ba75a958115c3b4eb598a10cfcc7e0
Declared price (base units)10000
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-10-01 01:03 UTC
Catalog-reported calls / payers (30d)3 / 2

2.Probe history

2026-09-072026-09-26
Figure 1. Probe timeline, last 30 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-09-26 22:40 UTCGETfail200467 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-26 04:40 UTCGETfail200489 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-25 13:40 UTCGETfail200469 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-24 16:40 UTCGETfail200385 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-23 22:40 UTCGETfail200392 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-23 04:40 UTCGETfail200671 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-22 13:40 UTCGETfail200693 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-21 16:40 UTCGETfail200549 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-20 22:40 UTCGETfail200640 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-20 04:40 UTCGETfail200481 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-19 13:40 UTCGETfail200473 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-18 22:40 UTCGETfail200492 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-18 04:40 UTCGETfail200642 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-17 13:40 UTCGETfail200361 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-16 16:40 UTCGETfail200149 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-15 22:40 UTCGETfail200374 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-15 04:40 UTCGETfail200197 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-14 16:40 UTCGETfail200146 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-13 22:40 UTCGETfail200130 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-13 13:40 UTCGETfail200130 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-12 16:40 UTCGETfail200327 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-12 04:40 UTCGETfail200174 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-11 16:40 UTCGETfail200429 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-10 23:40 UTCGETfail200628 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-10 14:40 UTCGETfail200133 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-09 23:40 UTCGETfail200282 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-09 05:40 UTCGETfail200648 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-08 17:40 UTCGETfail200315 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-08 05:40 UTCGETfail2002094 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-07 17:40 UTCGETfail5022320 msno_402HTTP 502 instead of 402 to an unpaid GET.

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 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 (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 mismatch
the response lacked fields the listing's output schema declares.
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).
3/3
Figure 2. Settle-through: one cell per paid attempt. Filled = settled on-chain, crossed = signed, and not settled on-chain.
L1 purchase history, newest first
Attempted atResultHTTPOn-chain txLatency
08-28 12:18settled (amount + payee)2000x66acd0b0…7c192445 ms
10000 units (≈ $0.01 USDC) · L2 mismatchWhose side: no failure (delivered)
08-21 08:32settled (amount + payee)2000x525b3bb6…6c7b1413 ms
10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)
08-14 09:56settled (amount + payee)2000x089f95b7…9c0c1438 ms
10000 units (≈ $0.01 USDC) · L2 mismatchWhose 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.

vet402: 3 of 3 paid attempts settled with an on-chain receipt, and 3 of those also returned a 2xx response. settled is the confirmed transfer; delivered is the response arriving. A measurement of what happened when vet402 paid this endpoint, not a recommendation. (api.robotsshop.io · measured 2026-08-28)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/2cdd7cfa-9835-478d-a5e5-217a71ba4f1e.svg)](https://vet402.com/observatory/e/2cdd7cfa-9835-478d-a5e5-217a71ba4f1e)

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