netz.halowerk.com/v1/bgp-origin
1.Catalog declaration
| Resource URL | https://netz.halowerk.com/v1/bgp-origin |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x2880edfff13100677bf97a3cbdf3bc34771c4e5e |
| Declared price (base units) | 4000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-04 13:40 UTC | POST | pass | 402 | 411 ms | — |
| 2026-10-03 13:40 UTC | POST | pass | 402 | 2329 ms | — |
| 2026-10-02 16:40 UTC | POST | pass | 402 | 350 ms | — |
| 2026-10-01 22:40 UTC | POST | pass | 402 | 551 ms | — |
| 2026-10-01 04:40 UTC | POST | pass | 402 | 714 ms | — |
| 2026-09-30 13:40 UTC | POST | pass | 402 | 526 ms | — |
| 2026-09-29 13:40 UTC | POST | pass | 402 | 333 ms | — |
| 2026-09-28 22:40 UTC | POST | pass | 402 | 613 ms | — |
| 2026-09-27 10:30 UTC | POST | pass | 402 | 341 ms | — |
| 2026-09-22 11:24 UTC | POST | pass | 402 | 328 ms | — |
| 2026-09-18 11:24 UTC | POST | pass | 402 | 322 ms | — |
| 2026-09-16 11:24 UTC | POST | pass | 402 | 349 ms | — |
| 2026-09-12 11:24 UTC | POST | pass | 402 | 450 ms | — |
| 2026-09-08 11:24 UTC | POST | fail | 400 | 361 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-03 11:24 UTC | POST | pass | 402 | 329 ms | — |
| 2026-08-31 11:24 UTC | POST | fail | 402 | 315 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
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 (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.
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 |
|---|---|---|---|---|
| 09-28 18:002026-09-28 18:00 UTC | settled (nonce-bound) | 200 | 0xc9da94bd…9c8e | 2625 ms |
| 4000 units (≈ $0.004 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/a258bba0-3c67-433f-ae1b-eedd476a2f8c)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.