tools.halowerk.com/v1/calendar/workdays
1.Catalog declaration
| Resource URL | https://tools.halowerk.com/v1/calendar/workdays |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x2880edfff13100677bf97a3cbdf3bc34771c4e5e |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:02 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-26 10:30 UTC | POST | pass | 402 | 358 ms | — |
| 2026-09-21 16:40 UTC | POST | pass | 402 | 365 ms | — |
| 2026-09-20 22:40 UTC | POST | pass | 402 | 1932 ms | — |
| 2026-09-20 04:40 UTC | POST | pass | 402 | 353 ms | — |
| 2026-09-19 13:40 UTC | POST | pass | 402 | 116 ms | — |
| 2026-09-18 22:40 UTC | POST | pass | 402 | 172 ms | — |
| 2026-09-18 04:40 UTC | POST | pass | 402 | 177 ms | — |
| 2026-09-17 13:40 UTC | POST | pass | 402 | 126 ms | — |
| 2026-09-16 16:40 UTC | POST | pass | 402 | 115 ms | — |
| 2026-09-15 22:40 UTC | POST | pass | 402 | 267 ms | — |
| 2026-09-15 04:40 UTC | POST | pass | 402 | 251 ms | — |
| 2026-09-14 16:40 UTC | POST | pass | 402 | 120 ms | — |
| 2026-09-13 22:40 UTC | POST | pass | 402 | 200 ms | — |
| 2026-09-13 13:40 UTC | POST | pass | 402 | 375 ms | — |
| 2026-09-12 16:40 UTC | POST | pass | 402 | 247 ms | — |
| 2026-09-12 04:40 UTC | POST | pass | 402 | 356 ms | — |
| 2026-09-11 16:40 UTC | POST | pass | 402 | 505 ms | — |
| 2026-09-10 23:40 UTC | POST | pass | 402 | 528 ms | — |
| 2026-09-10 14:40 UTC | POST | pass | 402 | 392 ms | — |
| 2026-09-09 23:40 UTC | POST | pass | 402 | 439 ms | — |
| 2026-09-09 05:40 UTC | POST | pass | 402 | 407 ms | — |
| 2026-09-08 17:40 UTC | POST | pass | 402 | 482 ms | — |
| 2026-09-08 05:40 UTC | POST | pass | 402 | 413 ms | — |
| 2026-09-07 17:40 UTC | POST | pass | 402 | 322 ms | — |
| 2026-09-07 05:40 UTC | POST | pass | 402 | 348 ms | — |
| 2026-09-06 17:40 UTC | POST | pass | 402 | 424 ms | — |
| 2026-09-06 05:40 UTC | POST | pass | 402 | 327 ms | — |
| 2026-09-05 17:40 UTC | POST | pass | 402 | 344 ms | — |
| 2026-09-05 05:40 UTC | POST | pass | 402 | 339 ms | — |
| 2026-09-04 17:40 UTC | POST | pass | 402 | 683 ms | — |
3.L1 — real purchases
1 of 1 paid attempts settled on-chain, and 1 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 (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.
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 |
|---|---|---|---|---|
| 08-14 10:112026-08-14 10:11 UTC | settled (amount + payee) | 200 | 0x31d90fd6…eb84 | 1259 ms |
| 1000 units (≈ $0.001 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/98eaab77-6da7-4a5e-a50e-85dc1fc85d30)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-08-14T10:11:51Z (UTC). The form starts with that time; add what you saw instead.