Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-09-02 · today

defillama.use.x402atlas.com/stablecoin-charts-all

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://defillama.use.x402atlas.com/stablecoin-charts-all
Source	cdp_bazaar
Declared method	GET
Network	eip155:8453
Receiving address	0xcb8025d951e5e45be7d288b658eeee6f05713006
Declared price (base units)	5000
Catalog status	active
First seen / last seen	2026-08-16 01:06 UTC / 2026-09-02 01:03 UTC
Catalog-reported calls / payers (30d)	2 / 1

2.Probe history

2026-09-012026-09-02

Figure 1. Probe timeline, last 2 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.

L0 probe history, newest first
Probed at	Method	Verdict	HTTP	Latency	Reason
2026-09-02 05:40 UTC	GET	pass	402	165 ms	—
2026-09-01 23:14 UTC	GET	pass	402	106 ms	—

3.L1 — real purchases

1 of 1 paid attempts settled with a receipt. Each settled row carries its on-chain transaction hash — the receipt is the evidence.

1/1

Figure 2. Settle-through: one cell per paid attempt. Filled = settled with an on-chain receipt, crossed = paid but no receipt.

L1 purchase history, newest first
Attempted at	Result	Receipt (tx)	Latency
09-02 01:012026-09-02 01:01 UTC	settled	0x7d7af7ca…0b1d	1066 ms
5000 units (≈ $0.005 USDC) · HTTP 200 · L2 mismatch

Embed this record

Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled and updates as the record grows. It states a measurement, not a rating.

[![vet402 receipt](https://vet402.com/api/badge/endpoint/3699e8bd-1d33-49f0-9eb4-204717119893.svg)](https://vet402.com/observatory/e/3699e8bd-1d33-49f0-9eb4-204717119893)

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.