commodity-macro.hergertsynthora.com/service
1.Catalog declaration
| Resource URL | https://commodity-macro.hergertsynthora.com/service |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x10800a5a5b9d72251566ec651e862a8b4b427de0 |
| Declared price (base units) | 50000 |
| Catalog status | delisted (since 2026-09-13 01:03 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-12 01:03 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-12 22:40 UTC | POST | fail | 402 | 674 ms | metadata_mismatch |
| 2026-09-12 04:40 UTC | POST | fail | 402 | 485 ms | metadata_mismatch |
| 2026-09-11 16:40 UTC | POST | fail | 402 | 448 ms | metadata_mismatch |
| 2026-09-10 23:40 UTC | POST | fail | 402 | 817 ms | metadata_mismatch |
| 2026-09-10 14:40 UTC | POST | fail | 402 | 393 ms | metadata_mismatch |
| 2026-09-09 23:40 UTC | POST | fail | 402 | 625 ms | metadata_mismatch |
| 2026-09-09 14:40 UTC | POST | fail | 402 | 444 ms | metadata_mismatch |
| 2026-09-08 17:40 UTC | POST | fail | 402 | 393 ms | metadata_mismatch |
| 2026-09-08 05:40 UTC | POST | fail | 402 | 793 ms | metadata_mismatch |
| 2026-09-07 17:40 UTC | POST | fail | 402 | 500 ms | metadata_mismatch |
| 2026-09-07 05:40 UTC | POST | fail | 402 | 601 ms | metadata_mismatch |
| 2026-09-06 17:40 UTC | POST | fail | 402 | 515 ms | metadata_mismatch |
| 2026-09-06 05:40 UTC | POST | fail | 402 | 531 ms | metadata_mismatch |
| 2026-09-05 17:40 UTC | POST | fail | 402 | 376 ms | metadata_mismatch |
| 2026-09-05 05:40 UTC | POST | fail | 402 | 444 ms | metadata_mismatch |
| 2026-09-04 17:40 UTC | POST | fail | 402 | 451 ms | metadata_mismatch |
| 2026-09-04 05:40 UTC | POST | fail | 402 | 364 ms | metadata_mismatch |
| 2026-09-03 17:40 UTC | POST | fail | 402 | 375 ms | metadata_mismatch |
| 2026-09-03 05:40 UTC | POST | fail | 402 | 436 ms | metadata_mismatch |
| 2026-09-02 17:40 UTC | POST | fail | 402 | 476 ms | metadata_mismatch |
| 2026-09-02 05:40 UTC | POST | fail | 402 | 441 ms | metadata_mismatch |
| 2026-09-01 23:40 UTC | POST | fail | 402 | 611 ms | metadata_mismatch |
| 2026-08-17 10:39 UTC | POST | pass | 402 | 349 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.
| Attempted at | Result | HTTP | Receipt (tx) | Latency |
|---|---|---|---|---|
| 08-17 12:482026-08-17 12:48 UTC | settled (amount + payee) | 200 | 0x452ae450…5c3b | 1605 ms |
| 50000 units (≈ $0.05 USDC) · L2 no_declaration | ||||
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/3a6e9b50-5004-4ef9-b162-07adc4aaa894)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-13 | 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.