handel.halowerk.com/v1/return-policy
Withdrawn from the catalog. This route is absent from a complete fetch of the public discovery catalog, so it is left out of the public L0 fail count.
1.Catalog declaration
| Resource URL | https://handel.halowerk.com/v1/return-policy |
| Source | cdp_bazaar |
| Declared method | POST |
| Catalog network | eip155:8453 |
| Receiving address | 0x2880edfff13100677bf97a3cbdf3bc34771c4e5e |
| Declared price (base units) | 10000 |
| Catalog status | delisted (since 2026-09-11 01:03 UTC) |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-09-10 01:03 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-10 17:40 UTC | POST | fail | 400 | 326 ms | no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail. |
| 2026-09-10 05:40 UTC | POST | fail | 400 | 657 ms | no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail. |
| 2026-09-09 17:40 UTC | POST | fail | 400 | 422 ms | no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail. |
| 2026-09-09 05:40 UTC | POST | fail | 400 | 704 ms | no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail. |
| 2026-09-08 14:40 UTC | POST | fail | 400 | 2493 ms | no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail. |
| 2026-09-07 23:40 UTC | POST | fail | 400 | 389 ms | no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail. |
| 2026-09-07 14:40 UTC | POST | fail | 400 | 398 ms | no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail. |
| 2026-09-06 23:40 UTC | POST | pass | 402 | 2329 ms | — |
| 2026-09-06 14:40 UTC | POST | pass | 402 | 629 ms | — |
| 2026-09-05 23:40 UTC | POST | pass | 402 | 363 ms | — |
| 2026-09-05 14:40 UTC | POST | pass | 402 | 238 ms | — |
| 2026-09-04 23:40 UTC | POST | pass | 402 | 204 ms | — |
| 2026-09-04 14:40 UTC | POST | pass | 402 | 201 ms | — |
| 2026-09-03 23:40 UTC | POST | pass | 402 | 343 ms | — |
| 2026-09-03 14:40 UTC | POST | pass | 402 | 395 ms | — |
| 2026-09-02 23:40 UTC | POST | pass | 402 | 514 ms | — |
| 2026-09-02 14:40 UTC | POST | pass | 402 | 414 ms | — |
| 2026-08-31 11:24 UTC | POST | fail | 402 | 111 ms | accepts_invalidRecorded before the 2026-09-29 change, when the probe read only the first 4,000 bytes of the 402 body; this body began like an x402 envelope, so the fail may be vet402's measuring error rather than the seller's. |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-11 | 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
A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
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. This listing is not active in the catalog, so a dispute filed on the record form does not put it on the re-probe list. The record stays on this page. The scheduled L0 run is at 10:30 UTC. This listing is not on that run. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.