Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-10-01 · 1 day ago

conc-exe.xyz/api/concierge-intel-whales

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://conc-exe.xyz/api/concierge-intel-whales
Source	cdp_bazaar
Declared method	POST
Network	eip155:8453
Receiving address	0xb85c83cc448edca8eb724f5d79b523faff9375a7
Declared price (base units)	20000
Catalog status	active
First seen / last seen	2026-08-14 08:39 UTC / 2026-10-02 01:04 UTC
Catalog-reported calls / payers (30d)	1 / 1

2.Probe history

2026-09-112026-10-01

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 at	Method	Verdict	HTTP	Latency	Reason
2026-10-01 22:40 UTC	POST	fail	402	103 ms	accepts_invalid402 without a payable accept: no PAYMENT-REQUIRED header; body has no accepts array.
2026-10-01 04:40 UTC	POST	fail	402	404 ms	accepts_invalid402 without a payable accept: no PAYMENT-REQUIRED header; body has no accepts array.
2026-09-30 13:40 UTC	POST	fail	402	173 ms	accepts_invalid402 without a payable accept: no PAYMENT-REQUIRED header; body has no accepts array.
2026-09-29 16:40 UTC	POST	fail	402	96 ms	accepts_invalid402 without a payable accept: no PAYMENT-REQUIRED header; body has no accepts array.
2026-09-28 22:40 UTC	POST	fail	402	69 ms	accepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change).
2026-09-28 04:40 UTC	POST	fail	402	94 ms	accepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change).
2026-09-27 13:40 UTC	POST	fail	402	283 ms	accepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change).
2026-09-26 16:40 UTC	POST	pass	402	196 ms	—
2026-09-25 22:40 UTC	POST	pass	402	312 ms	—
2026-09-25 04:40 UTC	POST	pass	402	117 ms	—
2026-09-24 13:40 UTC	POST	pass	402	2266 ms	—
2026-09-23 16:40 UTC	POST	pass	402	206 ms	—
2026-09-23 04:40 UTC	POST	pass	402	452 ms	—
2026-09-22 13:40 UTC	POST	pass	402	360 ms	—
2026-09-21 16:40 UTC	POST	pass	402	331 ms	—
2026-09-20 22:40 UTC	POST	pass	402	395 ms	—
2026-09-20 04:40 UTC	POST	pass	402	292 ms	—
2026-09-19 13:40 UTC	POST	pass	402	2587 ms	—
2026-09-18 16:40 UTC	POST	pass	402	83 ms	—
2026-09-17 22:40 UTC	POST	pass	402	375 ms	—
2026-09-17 13:40 UTC	POST	pass	402	415 ms	—
2026-09-16 16:40 UTC	POST	pass	402	157 ms	—
2026-09-15 16:40 UTC	POST	pass	402	1948 ms	—
2026-09-15 04:40 UTC	POST	pass	402	298 ms	—
2026-09-14 13:40 UTC	POST	pass	402	116 ms	—
2026-09-13 22:40 UTC	POST	pass	402	258 ms	—
2026-09-13 04:40 UTC	POST	pass	402	138 ms	—
2026-09-12 16:40 UTC	POST	pass	402	109 ms	—
2026-09-12 04:40 UTC	POST	pass	402	500 ms	—
2026-09-11 11:24 UTC	POST	pass	402	50 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 (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 match: the response had the fields the listing's output schema declares.
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 at	Result	HTTP	On-chain tx	Latency
09-12 06:002026-09-12 06:00 UTC	settled (nonce-bound)	200	0x286ae63f…09ea	1513 ms
20000 units (≈ $0.02 USDC) · L2 matchWhose 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 receipt](https://vet402.com/api/badge/endpoint/bf2a6ea5-c18e-40b7-81c3-4663ba364a2e.svg)](https://vet402.com/observatory/e/bf2a6ea5-c18e-40b7-81c3-4663ba364a2e)

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.