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

x402.coinstats.app/insights/fear-and-greed/chart

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://x402.coinstats.app/insights/fear-and-greed/chart
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0xa2ad8183209e5d2f7f0d8f995f5601a0bb5100c7
Declared price (base units)1000
Catalog statusactive
First seen / last seen2026-08-14 08:52 UTC / 2026-09-29 01:03 UTC
Catalog-reported calls / payers (30d)3 / 2

2.Probe history

2026-09-092026-09-29
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-09-29 04:40 UTCGETpass402349 ms—
2026-09-28 13:40 UTCGETpass402130 ms—
2026-09-27 16:40 UTCGETpass402155 ms—
2026-09-26 22:40 UTCGETpass4021936 ms—
2026-09-26 04:40 UTCGETpass40278 ms—
2026-09-25 13:40 UTCGETpass40260 ms—
2026-09-24 16:40 UTCGETpass40273 ms—
2026-09-23 22:40 UTCGETpass40258 ms—
2026-09-23 04:40 UTCGETpass40234 ms—
2026-09-22 16:40 UTCGETpass402350 ms—
2026-09-21 22:40 UTCGETpass402358 ms—
2026-09-21 04:40 UTCGETpass402241 ms—
2026-09-20 13:40 UTCGETpass402272 ms—
2026-09-19 16:40 UTCGETpass402297 ms—
2026-09-18 22:40 UTCGETpass402270 ms—
2026-09-18 04:40 UTCGETpass402186 ms—
2026-09-17 16:40 UTCGETpass402588 ms—
2026-09-16 22:40 UTCGETpass402274 ms—
2026-09-15 22:40 UTCGETpass402164 ms—
2026-09-15 13:40 UTCGETpass402217 ms—
2026-09-14 16:40 UTCGETpass402204 ms—
2026-09-14 04:40 UTCGETpass402274 ms—
2026-09-13 13:40 UTCGETpass402190 ms—
2026-09-12 22:40 UTCGETpass402250 ms—
2026-09-12 04:40 UTCGETpass402129 ms—
2026-09-11 16:40 UTCGETfail402405 msmetadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-11 04:40 UTCGETfail402245 msmetadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-10 14:40 UTCGETfail402222 msmetadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-09 23:40 UTCGETfail402451 msmetadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-09 14:40 UTCGETpass402204 ms—

3.L1 — real purchases

2 of 3 paid attempts settled on-chain, and 2 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.

1 of those paid attempts are held as inconclusive rather than counted against this seller (0 settled and answered 4xx, 0 answered 4xx with no settlement receipt, 1 answered 402 or 5xx while our own payer wallet was out of USDC, 2026-09-13 00:00 to 2026-09-15 23:49 UTC). A 4xx says the request was not one the server would accept, and we cannot rule out that the request was ours to get wrong: vet402 buys with no API key of the seller's, and sends a POST body only when the seller declares one. This is the same principle the methodology already applied to path_template URLs, applied to the body and the authentication header as well. The rows are not deleted and not hidden — they are below, with their status and HTTP code, and they are out of the denominator for delivered (corrections).

1 of the paid attempts failed on vet402's side (for example our wallet was out of USDC, or we did not send the input the listing declares). The rows stay in the table; the embeddable badge below leaves them out of its count and names them as “vet402 side”.

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.
settle_failed
vet402 signed a payment and got no settlement receipt back.
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).
payer_unfunded
held_reason in the export: a 402 or 5xx while vet402's Base wallet was out of USDC (2026-09-13 to 2026-09-15).
L2 mismatch
the response lacked fields the listing's output schema declares.
L2 not_checked
not checked: the paid request did not answer 200, so there was no response to check against the listing's output schema.
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).
2/3
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
09-27 12:02settled (nonce-bound)2000x7315aa41…8f401301 ms
1000 units (≈ $0.001 USDC) · L2 mismatchWhose side: no failure (delivered)
09-13 00:02settle_failed402—326 ms
1000 units (≈ $0.001 USDC) · L2 not_checkedWhose side: vet402's side
09-03 07:01settled (amount + payee)2000xeeb9063f…a1df1645 ms
1000 units (≈ $0.001 USDC) · L2 mismatchWhose side: no failure (delivered)

Embed this record

Run this endpoint? Show the settle-through record vet402 measured — the badge reads 2/2 settled · 2 delivered · vet402 side 1 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: 2 of 2 paid attempts settled with an on-chain receipt, and 2 of those also returned a 2xx response. settled is the confirmed transfer; delivered is the response arriving. 1 further paid attempt failed on vet402's side (for example its wallet was out of USDC, or it did not send the input the listing declares) and is left out of these counts. A measurement of what happened when vet402 paid this endpoint, not a recommendation. (x402.coinstats.app · measured 2026-09-27)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/1f59bfad-8b2f-4403-a1a5-d38ae4256ba9.svg)](https://vet402.com/observatory/e/1f59bfad-8b2f-4403-a1a5-d38ae4256ba9)

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

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.

About the purchase at 2026-09-03T07:01:40Z (UTC). The form starts with that time; add what you saw instead.

20–2,000 characters · 59 so far