touchstone.locomot.io

https://touchstone.locomot.io/timestamp

Shares a payout wallet with 22 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.

Verifiable timestamp (trustless proof-of-existence / freshness proof): bind a hash to a drand round for an anti-backdating receipt — proves data existed no earlier than a public instant, with no trusted timestamp authority. Privacy: stamp an opaque sha256 digest.

62
reliability

Reliability & health

Uptime and response time from our own unpaid probes, plus the reliability score built from them.

Uptime

100.0% avg
0% 50% 100% Mon 10 PMThu 3 AMSat 8 AMMon 6 PM

Response time

p50 132ms · p95 296ms
0ms 800ms 1600ms Mon 10 PMThu 3 AMSat 8 AMMon 6 PM
Data table
Reliability history per time bucket over the last 7 days (hourly).
Bucket Uptime Probes Response time
9/28/2026, 10:00:00 PM 100% 1 121ms
9/29/2026, 12:00:00 AM 100% 1 131ms
9/29/2026, 2:00:00 AM 100% 1 122ms
9/29/2026, 4:00:00 AM 100% 1 116ms
9/29/2026, 6:00:00 AM 100% 1 123ms
9/29/2026, 8:00:00 AM 100% 1 120ms
9/29/2026, 10:00:00 AM 100% 1 124ms
9/29/2026, 12:00:00 PM 100% 1 122ms
9/29/2026, 2:00:00 PM 100% 1 123ms
9/29/2026, 4:00:00 PM 100% 1 135ms
9/29/2026, 6:00:00 PM 100% 1 122ms
9/29/2026, 8:00:00 PM 100% 1 133ms
9/29/2026, 10:00:00 PM 100% 1 119ms
9/30/2026, 1:00:00 AM 100% 1 121ms
9/30/2026, 3:00:00 AM 100% 1 123ms
9/30/2026, 5:00:00 AM 100% 1 296ms
9/30/2026, 7:00:00 AM 100% 1 202ms
9/30/2026, 9:00:00 AM 100% 1 116ms
9/30/2026, 11:00:00 AM 100% 1 239ms
9/30/2026, 1:00:00 PM 100% 1 241ms
9/30/2026, 3:00:00 PM 100% 1 213ms
9/30/2026, 5:00:00 PM 100% 1 205ms
9/30/2026, 7:00:00 PM 100% 1 471ms
9/30/2026, 9:00:00 PM 100% 1 214ms
9/30/2026, 11:00:00 PM 100% 1 108ms
10/1/2026, 1:00:00 AM 100% 1 791ms
10/1/2026, 3:00:00 AM 100% 1 886ms
10/1/2026, 5:00:00 AM 100% 1 245ms
10/1/2026, 7:00:00 AM 100% 1 102ms
10/1/2026, 9:00:00 AM 100% 1 147ms
10/1/2026, 11:00:00 AM 100% 1 124ms
10/1/2026, 1:00:00 PM 100% 1 141ms
10/1/2026, 3:00:00 PM 100% 1 131ms
10/1/2026, 5:00:00 PM 100% 1 131ms
10/1/2026, 7:00:00 PM 100% 1 123ms
10/1/2026, 9:00:00 PM 100% 1 133ms
10/1/2026, 11:00:00 PM 100% 1 164ms
10/2/2026, 1:00:00 AM 100% 1 258ms
10/2/2026, 3:00:00 AM 100% 1 145ms
10/2/2026, 5:00:00 AM 100% 1 131ms
10/2/2026, 7:00:00 AM 100% 1 138ms
10/2/2026, 9:00:00 AM 100% 1 117ms
10/2/2026, 11:00:00 AM 100% 1 123ms
10/2/2026, 1:00:00 PM 100% 1 124ms
10/2/2026, 3:00:00 PM 100% 1 148ms
10/2/2026, 5:00:00 PM 100% 1 129ms
10/2/2026, 7:00:00 PM 100% 1 191ms
10/2/2026, 9:00:00 PM 100% 1 130ms
10/2/2026, 11:00:00 PM 100% 1 118ms
10/3/2026, 12:00:00 AM 100% 1 123ms
10/3/2026, 2:00:00 AM 100% 1 128ms
10/3/2026, 4:00:00 AM 100% 1 123ms
10/3/2026, 6:00:00 AM 100% 1 213ms
10/3/2026, 8:00:00 AM 100% 1 131ms
10/3/2026, 10:00:00 AM 100% 1 126ms
10/3/2026, 12:00:00 PM 100% 1 141ms
10/3/2026, 2:00:00 PM 100% 1 142ms
10/3/2026, 4:00:00 PM 100% 1 162ms
10/3/2026, 6:00:00 PM 100% 1 128ms
10/3/2026, 7:00:00 PM 100% 1 1577ms
10/3/2026, 9:00:00 PM 100% 1 127ms
10/3/2026, 11:00:00 PM 100% 1 152ms
10/4/2026, 1:00:00 AM 100% 1 135ms
10/4/2026, 2:00:00 AM 100% 1 134ms
10/4/2026, 4:00:00 AM 100% 1 124ms
10/4/2026, 6:00:00 AM 100% 1 126ms
10/4/2026, 8:00:00 AM 100% 1 132ms
10/4/2026, 1:00:00 PM 100% 1 136ms
10/4/2026, 3:00:00 PM 100% 1 124ms
10/4/2026, 5:00:00 PM 100% 1 140ms
10/4/2026, 7:00:00 PM 100% 1 137ms
10/4/2026, 8:00:00 PM 100% 1 129ms
10/5/2026, 2:00:00 AM 100% 1 123ms
10/5/2026, 7:00:00 AM 100% 1 132ms
10/5/2026, 9:00:00 AM 100% 1 165ms
10/5/2026, 11:00:00 AM 100% 1 132ms
10/5/2026, 1:00:00 PM 100% 1 139ms
10/5/2026, 2:00:00 PM 100% 1 154ms
10/5/2026, 4:00:00 PM 100% 1 136ms
10/5/2026, 6:00:00 PM 100% 1 186ms
62
Composite reliability — the weighted average of the dimensions below, on a 0–100 scale.
Availability
99

How often it was reachable when we probed it (weight 35%).

Latency
100

How quickly it answers when it is up — fast scores high (weight 20%).

Security
100

Whether it serves over working TLS / https (weight 15%).

Transparency
61

Whether the operator disclosed what it does — description, schema, identity (weight 15%).

Activity
2

Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).

Confidence 100% — how much probe evidence backs this score. A thin history is flagged, not hidden.

See the scoring methodology for exactly how each number is computed.

Payment

Currencies
USDC
Networks
base
Facilitator
unknown
SDK
unknown

Operator

Company
inferred — unknown
Jurisdiction
—
Registrar
—
Domain registered
—
Hosting network
CLOUDFLARENET
Hosting country
—

Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.

On-chain activity (base)

38
payments (30d)
0.08
USD volume (30d)
8
paying wallets (30d)

Payments per day

last payment 10/4/2026
0 5 10 Sep 8Sep 17Sep 28Oct 4
Data table
Settled payments per day.
Day Payments Volume (USD) Paying wallets
9/8/2026 3 0 2
9/12/2026 2 0 1
9/14/2026 10 0.02 2
9/15/2026 1 0.01 1
9/17/2026 3 0.01 3
9/21/2026 3 0.01 1
9/24/2026 1 0 1
9/25/2026 1 0 1
9/28/2026 2 0 1
9/29/2026 2 0.01 2
10/1/2026 2 0 2
10/3/2026 4 0.01 1
10/4/2026 4 0.01 2

Payout address changed 1 time, last on 8/20/2026

  • 0x9f5A…A36d → 0xa309…7674 (base) · 8/20/2026

A changed payout address is worth a second look — it can be routine, but it is also how a hijacked listing redirects funds.

This payout wallet is shared: figures cover all 23 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.

Linked by wallet — likely same operator

On-chain agent identity and the x402 endpoint that shares its settlement wallet.

Response schema
{}