toolshed.lemon-agent.dev/convert/json-yaml
1.Catalog declaration
| Resource URL | https://toolshed.lemon-agent.dev/convert/json-yaml |
| 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:02 UTC |
| Catalog-reported calls / payers (30d) | 4 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 16:40 UTC | POST | pass | 402 | 582 ms | — |
| 2026-09-27 22:40 UTC | POST | pass | 402 | 305 ms | — |
| 2026-09-27 04:40 UTC | POST | pass | 402 | 414 ms | — |
| 2026-09-26 13:40 UTC | POST | pass | 402 | 211 ms | — |
| 2026-09-25 22:40 UTC | POST | pass | 402 | 397 ms | — |
| 2026-09-25 04:40 UTC | POST | pass | 402 | 195 ms | — |
| 2026-09-24 13:40 UTC | POST | pass | 402 | 346 ms | — |
| 2026-09-23 16:40 UTC | POST | pass | 402 | 429 ms | — |
| 2026-09-22 22:40 UTC | POST | pass | 402 | 245 ms | — |
| 2026-09-22 04:40 UTC | POST | pass | 402 | 357 ms | — |
| 2026-09-21 13:40 UTC | POST | pass | 402 | 305 ms | — |
| 2026-09-20 16:40 UTC | POST | pass | 402 | 20 ms | — |
| 2026-09-19 22:40 UTC | POST | pass | 402 | 244 ms | — |
| 2026-09-19 04:40 UTC | POST | pass | 402 | 189 ms | — |
| 2026-09-18 16:40 UTC | POST | pass | 402 | 138 ms | — |
| 2026-09-17 22:40 UTC | POST | pass | 402 | 199 ms | — |
| 2026-09-17 04:40 UTC | POST | pass | 402 | 183 ms | — |
| 2026-09-16 16:40 UTC | POST | pass | 402 | 740 ms | — |
| 2026-09-15 16:40 UTC | POST | pass | 402 | 224 ms | — |
| 2026-09-14 22:40 UTC | POST | pass | 402 | 2204 ms | — |
| 2026-09-14 13:40 UTC | POST | pass | 402 | 323 ms | — |
| 2026-09-13 16:40 UTC | POST | pass | 402 | 256 ms | — |
| 2026-09-13 04:40 UTC | POST | pass | 402 | 110 ms | — |
| 2026-09-12 13:40 UTC | POST | pass | 402 | 238 ms | — |
| 2026-09-11 22:40 UTC | POST | pass | 402 | 555 ms | — |
| 2026-09-11 13:40 UTC | POST | pass | 402 | 401 ms | — |
| 2026-09-10 17:40 UTC | POST | pass | 402 | 288 ms | — |
| 2026-09-10 05:40 UTC | POST | pass | 402 | 537 ms | — |
| 2026-09-09 17:40 UTC | POST | pass | 402 | 300 ms | — |
| 2026-09-09 05:40 UTC | POST | pass | 402 | 286 ms | — |
3.L1 — real purchases
2 of 3 paid attempts settled with a receipt, and 2 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.
settle_failed- vet402 signed a payment and got no settlement receipt back.
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 no_declaration- the listing declares no output schema to check the response against.
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.
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 12:022026-09-23 12:02 UTC | settled (nonce-bound)tx from our index | 200 | 0x2fcfc221…e6a0 | 874 ms |
| 2000 units (≈ $0.002 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-12 00:002026-09-12 00:00 UTC | settle_failed | 503 | — | 859 ms |
| 2000 units (≈ $0.002 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
| 09-03 12:082026-09-03 12:08 UTC | settled (amount + payee)tx from our index | 200 | 0x1e75eb6d…a9f3 | 534 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 2/3 settled · 2 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/cc3edc94-f8b3-46ca-8ac0-7b07c2af2093)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-03T12:08:46Z (UTC). The form starts with that time; add what you saw instead.