PulseFeed x402 Trust Oracle

https://pulsefeed.dev/a2a

Ask before you pay: PulseFeed tells an AI agent whether an x402 payment endpoint is safe to pay — liveness, anomaly scan (receiver-address changes between observations, catalog price vs. challenge price, invalid receivers, asset/network mismatch), on-chain receiver verification on Base, and an open 0-100 Trust Score. Built on a continuous independent audit of the x402 ecosystem (16257 endpoints probed of 25976 tracked, 17% of probed dead or invalid) plus a security audit of the MCP server ecosystem.

51
reliability

Reliability & health

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

7 days 30 days

Uptime

85.7% avg
0% 50% 100% Aug 15Aug 17Aug 19Aug 21

Response time

p50 465ms · p95 526ms
0ms 450ms 900ms Aug 15Aug 17Aug 19Aug 21
Data table
Reliability history per time bucket over the last 30 days (daily).
Bucket Uptime Probes Response time
8/15/2026, 12:00:00 AM 0% 1 —
8/16/2026, 12:00:00 AM 100% 1 485ms
8/17/2026, 12:00:00 AM 100% 1 331ms
8/18/2026, 12:00:00 AM 100% 1 853ms
8/19/2026, 12:00:00 AM 100% 20 406ms
8/20/2026, 12:00:00 AM 100% 21 330ms
8/21/2026, 12:00:00 AM 100% 1 109ms
51
Composite reliability — the weighted average of the dimensions below, on a 0–100 scale.
Availability
98

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

Latency
94

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

Security
94

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

Transparency
42

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

Activity
not yet measured

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 92% — 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
—
Networks
—
Facilitator
unknown
SDK
unknown

Operator

Company
inferred — unknown
Jurisdiction
—
Registrar
—
Domain registered
—
Hosting network
DE-FORNEX
Hosting country
DE

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.

x402trustsecuritypaymentsverificationagentic-commercethreat-intelligenceincidentson-chain