Skip to main content
vet402
MenuClose
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-11-11 · 1 day ago
vet402Back to the registerMethodology

defi.halowerk.com/bridge/quote

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://defi.halowerk.com/bridge/quote
Sourcecdp_bazaar
Declared methodPOST
Catalog networkeip155:8453
Receiving address0x2880edfff13100677bf97a3cbdf3bc34771c4e5e
Declared price (base units)8000
Catalog statusactive
First seen / last seen2026-08-14 08:52 UTC / 2026-11-12 20:06 UTC
Catalog-reported calls / payers (30d)4 / 4

2.Probe history

2026-08-302026-11-11
Figure 1. Probe timeline, last 30 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap. Marks closer than one mark width are stepped down one lane.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-11-11 04:40 UTCPOSTpass402451 ms—
2026-11-08 22:40 UTCPOSTpass402436 ms—
2026-11-06 16:40 UTCPOSTpass402355 ms—
2026-11-04 13:40 UTCPOSTpass402630 ms—
2026-11-01 13:40 UTCPOSTpass402381 ms—
2026-10-30 13:40 UTCPOSTpass402552 ms—
2026-10-28 13:40 UTCPOSTpass402382 ms—
2026-10-26 18:40 UTCPOSTpass402365 ms—
2026-10-25 00:40 UTCPOSTpass402457 ms—
2026-10-22 22:40 UTCPOSTpass402330 ms—
2026-10-21 13:40 UTCPOSTpass402433 ms—
2026-10-20 04:40 UTCPOSTpass402435 ms—
2026-09-10 17:40 UTCPOSTfail400319 msno_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 UTCPOSTfail400645 msno_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 UTCPOSTfail400422 msno_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 UTCPOSTfail400571 msno_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 UTCPOSTfail4002698 msno_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 UTCPOSTfail400345 msno_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 UTCPOSTfail400366 msno_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 UTCPOSTpass4022352 ms—
2026-09-06 14:40 UTCPOSTpass402390 ms—
2026-09-05 23:40 UTCPOSTpass402379 ms—
2026-09-05 14:40 UTCPOSTpass402421 ms—
2026-09-04 23:40 UTCPOSTpass402406 ms—
2026-09-04 14:40 UTCPOSTpass402390 ms—
2026-09-03 23:40 UTCPOSTpass402349 ms—
2026-09-03 14:40 UTCPOSTpass402381 ms—
2026-09-02 23:40 UTCPOSTpass4022382 ms—
2026-09-02 14:40 UTCPOSTpass402674 ms—
2026-08-30 11:24 UTCPOSTfail402106 msaccepts_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 deliverable 2xx response (delivered: other than 202 Accepted with a non-empty body). 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 matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count. The Stellar re-read checks payer, payee, amount and asset. A row reads as amount + payee when the re-read matched payer, payee, amount and asset and did not bind a one-time value. That tier holds rows from before 2026-09-04 and Stellar rows. They keep the settled label rather than being demoted (methodology). settled is the transfer vet402 confirmed on-chain. delivered is a 2xx other than 202 with a non-empty body. A settled row whose paid request answered 5xx counts as settled and not as delivered. definitions.

Terms in this table

settled (nonce-bound)
vet402 re-read the transfer on-chain in that chain's pinned settlement asset, and the on-chain re-read matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count.
L2 no_declaration
the listing's output schema gave vet402 nothing to check this response against (no schema, a schema with no required keys and no example properties, or example properties with a content type that is not JSON). vet402 checks the current 402 from the seller before the catalog schema. An output example in the 402 (extensions.bazaar.info.output.example) is part of that check when the catalog also declares an output.
Whose side
the same words as the seller page: seller's side only after failures on two different days (UTC), marked “attribution under review”; vet402's side; or not sorted (the rules).
1/1
Figure 2. Settle-through: one cell per paid attempt. Filled = settled on-chain, crossed = signed, and not settled on-chain.
L1 purchase history, newest first
Attempted atResultHTTPOn-chain txPayment chainLatency
10-20 06:01settled (nonce-bound)2000x01f69946…d7e7Base2692 ms
8000 units (≈ $0.008 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.

vet402: 1 of 1 paid attempts settled with an on-chain receipt, and 1 of those also returned a deliverable HTTP 2xx response. settled is the confirmed transfer; delivered is a 2xx other than 202 with a non-empty body. A measurement of what happened when vet402 paid this endpoint, not a recommendation. (defi.halowerk.com · measured 2026-10-20)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/45e5bddf-7617-4256-a95a-c202a563027d.svg)](https://vet402.com/observatory/e/45e5bddf-7617-4256-a95a-c202a563027d)

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint. We first send one confirmation email; nothing else goes out until you confirm.

4.Catalog listing events

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-09-11delisted{"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. A dispute filed on the record form puts an active listing on a priority list. L0 runs probe that list before their ordinary queue, one run at a time. A listing whose URL has an unfilled path parameter is not put on that list. One run measures up to 50 priority listings, at most 5 from one site. Published fails whose catalog declaration changed, or that rest on probes recorded under earlier rules, take places first, and disputes fill the places left. A listing probed in the past 60 minutes waits for a later run. A dispute that no run reaches within 7 days leaves the list. The scheduled L0 run is at 10:30 UTC, and an L0 run at another time can measure the listing first. The record stays on this page. When a run measures the listing, the new probe is added to its history. 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.

About the purchase at 2026-10-20T06:01:48Z (UTC). The form starts with that time; add what you saw instead.

20–2,000 characters · 59 so far