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://readx.sh/api/:name/tweets/:id

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 13000 7000 15 Aug 2026 — 0.010000 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.010000 USDC eip155:8453

Changes

  • 15 Aug 2026

    Reachability changed: status from unreachable to active. unreachable → active Observed 15 Aug 2026, 06:15 UTC · recorded by crawler · scoring in force then: v1

  • 15 Aug 2026

    First observed — this is where our record of this endpoint begins. 139c288c629564f33fc416918b345f974ac0d1a7fbb7b9ad6938397a4ce70362 Observed 15 Aug 2026, 06:15 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)
≈50.00%
Median response (sampled)
≈1133 ms
Slowest 5% (sampled)
≈1133 ms
Probe samples
≈2
We were not observing this endpoint before 15 Aug 2026 not observing yet 100% 0% 15 Aug 2026 — ≈50.00% over 2 samples 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 1360 ms 0 15 Aug 2026 — ≈1133 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, 14:36 UTC
Probes recorded 3
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.