api.seneschal.space/v1/q/zec/pools
1.Catalog declaration
| Resource URL | https://api.seneschal.space/v1/q/zec/pools |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x46ba634261566cf242c853d1f49511f9268ba674 |
| Declared price (base units) | 1000 |
| Catalog status | delisted (since 2026-09-27 01:02 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-26 01:02 UTC |
| Catalog-reported calls / payers (30d) | 12 / 7 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-26 13:40 UTC | GET | fail | — | 10002 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 765 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 402 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 968 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 405 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 396 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 8134 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 353 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 2354 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 367 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 527 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 2374 ms | — |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 2457 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 509 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 216 ms | — |
| 2026-09-15 13:40 UTC | GET | pass | 402 | 1108 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 355 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 391 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 503 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 419 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 769 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 581 ms | — |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 352 ms | — |
| 2026-09-10 17:40 UTC | GET | pass | 402 | 662 ms | — |
| 2026-09-09 23:40 UTC | GET | pass | 402 | 499 ms | — |
| 2026-09-09 14:40 UTC | GET | pass | 402 | 116 ms | — |
| 2026-09-08 23:40 UTC | GET | pass | 402 | 732 ms | — |
| 2026-09-08 14:40 UTC | GET | pass | 402 | 339 ms | — |
| 2026-09-07 17:40 UTC | GET | pass | 402 | 481 ms | — |
| 2026-09-07 05:40 UTC | GET | pass | 402 | 431 ms | — |
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 (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.
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 match- the response had the fields the listing's output schema declares.
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 | On-chain tx | Latency |
|---|---|---|---|---|
| 09-16 18:022026-09-16 18:02 UTC | settled (nonce-bound) | 200 | 0xe9bd5f7e…dab8 | 1754 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-10 12:092026-09-10 12:09 UTC | settled (nonce-bound) | 200 | 0x3c368fd3…7960 | 1581 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-03 19:002026-09-03 19:00 UTC | settled (amount + payee) | 200 | 0xd524f5b9…df58 | 5953 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose 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.
[](https://vet402.com/observatory/e/c91e875a-d7b2-4dab-9ab8-5a637fc98b24)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-27 | 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.