Skip to main content
vet402
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-03 · today
vet402Back to the registerMethodology

pulsefeed.dev/trust

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://pulsefeed.dev/trust
Sourcecdp_bazaar
Declared methodGET
Networkbase
Receiving address0x7f5f784ba98cecfc0ba4336f0e48222a3d4d69a8
Declared price (base units)—
Catalog statusactive
First seen / last seen2026-08-14 08:52 UTC / 2026-10-03 01:04 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-09-072026-10-03
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-10-03 10:30 UTCGETpass402551 ms—
2026-09-26 13:40 UTCGETfail200446 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-25 16:40 UTCGETfail200595 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-24 22:40 UTCGETfail200469 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-24 04:40 UTCGETfail200542 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-23 13:40 UTCGETfail200621 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-22 16:40 UTCGETfail200491 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-21 22:40 UTCGETfail200556 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-21 04:40 UTCGETfail200792 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-20 13:40 UTCGETfail200468 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-19 16:40 UTCGETfail200488 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-18 22:40 UTCGETfail200520 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-18 13:40 UTCGETfail200583 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-17 16:40 UTCGETfail200763 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-16 22:40 UTCGETfail200455 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-16 13:40 UTCGETfail200760 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-15 13:40 UTCGETfail200625 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-14 16:40 UTCGETfail200720 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-14 04:40 UTCGETfail2001172 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-13 13:40 UTCGETfail200518 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-12 22:40 UTCGETfail200550 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-12 04:40 UTCGETfail200508 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-11 16:40 UTCGETfail200516 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-11 04:40 UTCGETfail200506 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-10 14:40 UTCGETfail200448 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-09 23:40 UTCGETfail200647 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-09 14:40 UTCGETfail200497 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-08 23:40 UTCGETfail200858 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-08 05:40 UTCGETfail200662 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-07 17:40 UTCGETfail200597 msno_402HTTP 200 instead of 402 to an unpaid GET.

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).
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 txLatency
08-28 12:20settled (amount + payee)2000xf1da8dc5…bd632066 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.

vet402: 1 of 1 paid attempts settled with an on-chain receipt, and 1 of those also returned a 2xx response. settled is the confirmed transfer; delivered is the response arriving. A measurement of what happened when vet402 paid this endpoint, not a recommendation. (pulsefeed.dev · measured 2026-08-28)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/2360dd3a-9807-4724-b175-c73dd86b93eb.svg)](https://vet402.com/observatory/e/2360dd3a-9807-4724-b175-c73dd86b93eb)

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-10-03relisted{"status":"delisted"}{"status":"active"}
2026-09-28delisted{"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.

20–2,000 characters · 0 so far