Skip to content
PulseFeed

PulseFeed Trust Score

An open, independently-computed trust rating for x402 payment endpoints.

Standard v1.0 · range 0–100

The PulseFeed Trust Score is a 0–100 summary and a canonical band computed from recorded endpoint probes, risk signals and available receiver checks. It helps an agent review an endpoint before deciding to pay. It does not establish current availability or guarantee delivery of a purchased result.

For cached results, inspect the individual record’s lastChecked. A daily crawl is not a revalidation of every endpoint. See the dated ecosystem snapshot for current counts, units and denominators.

Canonical bands

BandRangeMeaning
Verified85–100 + safeLatest observation: valid x402 challenge, clean recorded risk scan and an established receiver signal. Not a guarantee of current availability or delivery of a purchased result.
Trusted70–84 + safeLatest observation: valid x402 challenge with a positive recorded track record. Not a guarantee of current availability or delivery of a purchased result.
Caution35–69Latest observation has caveats (thin history, medium risk flag, or unproven receiver). Review its age and evidence before paying.
Avoid0–34 or high-riskDead, invalid, or flagged high-risk (payTo hijack, bait-and-switch, honeypot). Do not pay.
Unknownnot indexedNot in our index yet — no cached verdict. Use a live /trust check.

Bands are always consistent with the pay/avoid verdict: a high raw score never shows as "Verified" if a high-risk flag forces Avoid.

How the score is computed (transparent)

FactorEffectDetail
Live & valid x402 challengebase 55The endpoint actually returns a correct x402 402 challenge in our independent probe.
Uptime / reputationup to +30Share of healthy probes in our observation history (or an external 30-day uptime).
Multi-source corroboration+10Listed in two or more catalogs (Bazaar and 402index).
Fast response+5Responds in under 1.5 s.
On-chain established receiver+5Available receiver signal: Base uses USDC/account checks and best-effort history; the configured Solana lookup uses SPL USDC balance only. Cached profiles can be partial or pending.
Stable receiver over time+5 / −5A payTo that stays the same over time adds; a volatile one subtracts.
Medium-risk anomaly flagcap 55Creeping price increases, an unconfirmed receiver and similar signals cap the verdict at caution.
High-risk anomaly flagcap 25payTo hijack, bait-and-switch, honeypot or a foreign asset: the verdict is avoid even if the endpoint is live.

Receiver lookup coverage

LookupChecksLimits
live · Base mainnetUSDC balance; account code and nonce; best-effort incoming USDC historyIncoming transfer history depends on RPC support and may be unavailable; a receiver profile is not proof of delivery of a purchased result.
live · Solana via the configured RPC (mainnet by default)SPL USDC account balanceNo transfer-history check. The configured RPC and USDC mint do not establish support for every Solana cluster; inspect the returned profile and note.
cached · Previously observed receiver profilesstored per-record profile and observation time, where availablePartial coverage: profiles can be pending, unknown or absent. The aggregate's legacy non-base bucket is not proof that every non-Base network is unsupported by the live lookup.

Consume it

GET /verify?endpoint=Free cached score + verdict + band
GET /trust?endpoint=Live score + band + security scan + on-chain receiver (paid)
GET /trust/datasetBand per service, in bulk (paid)
GET /badge.svg?endpoint=Embeddable Trust Score badge
GET /trust-score.jsonThis spec, machine-readable
Cite it: PulseFeed Trust Score v1.0 — https://pulsefeed.dev/trust-score

Full scoring methodology: /methodology · Live ecosystem: /status · State of x402: /reports · Machine-readable: /trust-score.json
The PulseFeed Trust Score is versioned; changes to the formula bump the version. Independent, transparent, and free to reference.