pulse.chainverdict.xyz

https://pulse.chainverdict.xyz/v1/archive/full

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

The complete daily observation history of third-party x402 endpoints since first observation, with the Merkle root of each day. Each root is chained to the previous day and timestamped into Bitcoin via OpenTimestamps, so the archive can be verified as having existed on the stated dates rather than assembled later. The most recent 7 days are free at /v1/datasets/day/{day}; the manifest and verification method are free at /v1/datasets/manifest.

61
reliability

Reliability & health

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

7 days 30 days

Uptime

100.0% avg
0% 50% 100% Aug 24Aug 26Aug 27Aug 29

Response time

p50 130ms · p95 286ms
0ms 150ms 300ms Aug 24Aug 26Aug 27Aug 29
Data table
Reliability history per time bucket over the last 30 days (daily).
Bucket Uptime Probes Response time
8/24/2026, 12:00:00 AM 100% 7 237ms
8/25/2026, 12:00:00 AM 100% 16 142ms
8/26/2026, 12:00:00 AM 100% 10 96ms
8/27/2026, 12:00:00 AM 100% 13 83ms
8/28/2026, 12:00:00 AM 100% 21 111ms
8/29/2026, 12:00:00 AM 100% 5 115ms
61
Composite reliability — the weighted average of the dimensions below, on a 0–100 scale.
Availability
100

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
0

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
Cloudflare, Inc.
Domain registered
2026-08-06
Hosting network
RS-1125
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)

153
payments (30d)
6.59
USD volume (30d)
7
paying wallets (30d)

Payments per day

last payment 8/29/2026
0 100 200 Aug 7Aug 14Aug 22Aug 29
Data table
Settled payments per day.
Day Payments Volume (USD) Paying wallets
8/7/2026 4 0.27 1
8/8/2026 1 0.12 1
8/9/2026 1 0.12 1
8/10/2026 1 0.12 1
8/11/2026 108 3.28 1
8/12/2026 2 0.12 2
8/13/2026 3 0.13 2
8/14/2026 1 0.12 1
8/15/2026 1 0.12 1
8/16/2026 1 0.12 1
8/17/2026 3 0.13 2
8/18/2026 5 0.15 2
8/19/2026 1 0.12 1
8/20/2026 1 0.12 1
8/21/2026 1 0.12 1
8/22/2026 1 0.12 1
8/23/2026 6 0.18 2
8/24/2026 3 0.62 2
8/25/2026 1 0.12 1
8/26/2026 3 0.13 3
8/27/2026 1 0 1
8/28/2026 3 0.13 2
8/29/2026 1 0.12 1

This payout wallet is shared: figures cover all 51 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.

https://chainverdict.xyz/v1/wallet/dossier/:address x402 endpoint https://chainverdict.xyz/v1/verify/payment/:tx x402 endpoint https://chainverdict.xyz/v1/verify/token/:q x402 endpoint https://pulse.chainverdict.xyz/v1/attest x402 endpoint https://chainverdict.xyz/v1/data/portfolio/:addr x402 endpoint https://chainverdict.xyz/v1/validate/iban/:iban x402 endpoint https://chainverdict.xyz/v1/validate/lei/:lei x402 endpoint https://trade.chainverdict.xyz/v1/container/validate x402 endpoint
Response schema 
{
  "additionalProperties": true,
  "type": "object"
}