tx402 tools

How has this x402 endpoint's price changed?

See how an x402 endpoint's price, payout address, availability and latency have changed over time, with every terms change dated and recorded.

We look this endpoint up in what we have already observed. Nothing is fetched from the endpoint — History never probes.

Exact record

Every entry below is a change we observed, written once to an append-only log and never edited. The dates are the moment we observed the change. This is the record an operator would be shown.

Sampled telemetry

These figures are estimates. They come from a sampled dataset: each stored measurement stands for several real ones, and old measurements age out. They are good enough to describe a trend and are not evidence about any particular request.

https://api.hyperextend.xyz/v1/candles/BTC/1m/latest

Exact record

exact · append-only record

Every entry below is a change we observed, written once to an append-only log and never edited. The dates are the moment we observed the change. This is the record an operator would be shown.

Short record. We first observed this endpoint today, so this window is almost entirely before our record begins.

We were not observing this endpoint before 15 Aug 2026 not observing yet 2600 1400 15 Aug 2026 — 0.002000 USDC 16 Jul 2026 15 Aug 2026
Price in atomic units. Each marker is a change we observed, on the date we observed it. The line holds flat between observations because the price did.
Show the observed prices
Observed atPriceNetwork
15 Aug 2026, 04:00 UTC 0.002000 USDC eip155:8453

Changes

  • 15 Aug 2026

    First observed — this is where our record of this endpoint begins. f2ac480d50497882064bf5a9d613cb17bb12f21463de7f803ef2323457ae8aa5 Observed 15 Aug 2026, 05:30 UTC · recorded by crawler · scoring in force then: v1

Written to an append-only log that a database trigger will not let anyone update or delete. A mistake is corrected by appending a correction, so nothing here can be quietly rewritten.

Sampled telemetry

sampled · estimate

These figures are estimates. They come from a sampled dataset: each stored measurement stands for several real ones, and old measurements age out. They are good enough to describe a trend and are not evidence about any particular request.

Availability (30d, sampled)
≈100.00%
Median response (sampled)
≈1141 ms
Slowest 5% (sampled)
≈1141 ms
Probe samples
≈1
We were not observing this endpoint before 15 Aug 2026 not observing yet 100% 0% 15 Aug 2026 — ≈100.00% over 1 sample 16 Jul 2026 15 Aug 2026
≈ Estimated share of probes that were answered, per bucket. Sampled — a fainter bar rests on fewer samples.
We were not observing this endpoint before 15 Aug 2026 not observing yet 1369 ms 0 15 Aug 2026 — ≈1141 ms median over 1 sample 16 Jul 2026 15 Aug 2026
≈ Estimated median (solid dashes) and 95th percentile (faint) response time of successful probes. Sampled.
Aggregated from a sampled dataset by total sample weight, not by counting stored rows. Retention is bounded, so an old window thins out. These figures describe a trend; they are not a record of any particular request.

What we have

First observed 15 Aug 2026today — our record begins here
Last observed 15 Aug 2026, 05:30 UTC
Probes recorded 1
Window requested last 30 days
Contains sampled figures yes — availability and latency are estimates

Markdown · JSON · price and recipient changes are exact; availability and latency are sampled.