toolshed.lemon-agent.dev/convert/csv-json
1.Catalog declaration
| Resource URL | https://toolshed.lemon-agent.dev/convert/csv-json |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x0adc7adac7bbaffffbd73505711e42378c4f9f9e |
| Declared price (base units) | 2000 |
| Catalog status | active |
| First seen / last seen | 2026-08-21 01:57 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 22:40 UTC | POST | pass | 402 | 295 ms | — |
| 2026-09-28 04:40 UTC | POST | pass | 402 | 496 ms | — |
| 2026-09-27 13:40 UTC | POST | pass | 402 | 212 ms | — |
| 2026-09-26 16:40 UTC | POST | pass | 402 | 1881 ms | — |
| 2026-09-25 22:40 UTC | POST | pass | 402 | 324 ms | — |
| 2026-09-25 04:40 UTC | POST | pass | 402 | 286 ms | — |
| 2026-09-24 13:40 UTC | POST | pass | 402 | 235 ms | — |
| 2026-09-23 16:40 UTC | POST | pass | 402 | 209 ms | — |
| 2026-09-22 22:40 UTC | POST | pass | 402 | 250 ms | — |
| 2026-09-22 11:24 UTC | POST | pass | 402 | 196 ms | — |
| 2026-09-18 11:24 UTC | POST | pass | 402 | 391 ms | — |
| 2026-09-16 11:24 UTC | POST | pass | 402 | 323 ms | — |
| 2026-09-12 11:24 UTC | POST | pass | 402 | 251 ms | — |
| 2026-09-08 11:24 UTC | POST | pass | 402 | 188 ms | — |
| 2026-09-04 11:24 UTC | POST | pass | 402 | 199 ms | — |
3.L1 — real purchases
1 of 1 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.
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-23 00:002026-09-23 00:00 UTC | settled (nonce-bound)tx from our index | 200 | 0x3ae958d2…b0be | 1055 ms |
| 2000 units (≈ $0.002 USDC) · L2 no_declarationWhose 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/3521c9d1-323e-4f8f-89a0-018ad7a1e169)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-23T00:00:29Z (UTC). The form starts with that time; add what you saw instead.