toolshed.lemon-agent.dev/convert/json-toml
1.Catalog declaration
| Resource URL | https://toolshed.lemon-agent.dev/convert/json-toml |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x0adc7adac7bbaffffbd73505711e42378c4f9f9e |
| Declared price (base units) | 4000 |
| Catalog status | active |
| First seen / last seen | 2026-09-03 01:03 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-27 10:30 UTC | POST | pass | 402 | 179 ms | — |
| 2026-09-22 11:24 UTC | POST | pass | 402 | 140 ms | — |
| 2026-09-18 16:40 UTC | POST | pass | 402 | 292 ms | — |
| 2026-09-17 22:40 UTC | POST | pass | 402 | 641 ms | — |
| 2026-09-17 13:40 UTC | POST | pass | 402 | 465 ms | — |
| 2026-09-16 16:40 UTC | POST | pass | 402 | 107 ms | — |
| 2026-09-15 16:40 UTC | POST | pass | 402 | 279 ms | — |
| 2026-09-15 04:40 UTC | POST | pass | 402 | 239 ms | — |
| 2026-09-14 13:40 UTC | POST | pass | 402 | 586 ms | — |
| 2026-09-13 22:40 UTC | POST | pass | 402 | 369 ms | — |
| 2026-09-13 04:40 UTC | POST | pass | 402 | 331 ms | — |
| 2026-09-12 16:40 UTC | POST | pass | 402 | 2183 ms | — |
| 2026-09-12 04:40 UTC | POST | pass | 402 | 230 ms | — |
| 2026-09-11 13:40 UTC | POST | pass | 402 | 240 ms | — |
| 2026-09-10 23:40 UTC | POST | pass | 402 | 381 ms | — |
| 2026-09-10 14:40 UTC | POST | pass | 402 | 586 ms | — |
| 2026-09-09 17:40 UTC | POST | pass | 402 | 2300 ms | — |
| 2026-09-09 05:40 UTC | POST | pass | 402 | 275 ms | — |
| 2026-09-08 17:40 UTC | POST | pass | 402 | 317 ms | — |
| 2026-09-08 05:40 UTC | POST | pass | 402 | 446 ms | — |
| 2026-09-07 14:40 UTC | POST | pass | 402 | 213 ms | — |
| 2026-09-06 23:40 UTC | POST | pass | 402 | 81 ms | — |
| 2026-09-06 14:40 UTC | POST | pass | 402 | 222 ms | — |
| 2026-09-05 23:40 UTC | POST | pass | 402 | 260 ms | — |
| 2026-09-05 14:40 UTC | POST | pass | 402 | 255 ms | — |
| 2026-09-04 23:40 UTC | POST | pass | 402 | 216 ms | — |
| 2026-09-04 14:40 UTC | POST | pass | 402 | 86 ms | — |
| 2026-09-03 23:40 UTC | POST | pass | 402 | 298 ms | — |
| 2026-09-03 14:40 UTC | POST | pass | 402 | 24 ms | — |
| 2026-09-03 05:40 UTC | POST | pass | 402 | 615 ms | — |
3.L1 — real purchases
0 of 1 paid attempts settled with a receipt, and 0 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.
Terms in this table
settle_failed- vet402 signed a payment and got no settlement receipt back.
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-06 19:022026-09-06 19:02 UTC | settle_failed | 503 | — | 525 ms |
| 4000 units (≈ $0.004 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
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-06T19:02:01Z (UTC). The form starts with that time; add what you saw instead.