Paywary

How scores are computed

Scores measure reliability and honesty, not output quality. A score of 100 means an endpoint reliably answers, serves a valid x402 challenge, quotes the price it lists, keeps the same wallet, and delivers after payment. It says nothing about whether the data it returns is any good.

Scores cannot be bought

There is no listing fee, no verification tier, and no way for a seller to submit or edit a score. Every number comes from our own probes of endpoints discovered in public facilitator catalogs (Coinbase CDP Bazaar and PayAI). Sellers can only improve a score by being up, honest and stable. Facilitator-reported popularity figures are shown for context but never enter the score.

Data collection

Components and weights

Each component is a value from 0 to 1. The score is the weighted sum times 100. When a component has no data (for example delivery before any paid probe), it is excluded and its weight is spread over the remaining components in proportion.

ComponentWeightDefinition
Uptime, 7 days20%Share of our unpaid probes in the last 7 days that got an HTTP response other than a 5xx or 429. Curved so that downtime bites: 99% uptime scores about 97, 95% about 85, 90% about 72, 70% about 25, and 50% or less scores zero.
Uptime, 30 days15%The same measure over 30 days.
Valid x402 challenge15%Share of responses whose 402 challenge was a spec-valid x402 payment requirement for the option we would pay (exact scheme, Base, USDC). A 200 with no payment required, a 404, or a malformed challenge all count against this.
Price honesty15%Share of comparable probes where the price quoted in the 402 matched the price listed in the discovery catalog, and (once paid probes run) where the amount settled on chain matched the quote. A mismatch on a POST endpoint whose price can depend on the body counts half.
Delivery after payment15%Share of paid probes that settled and then returned a 2xx response. Not available until an endpoint has been paid; until then this weight is spread over the other components.
Wallet stability10%Starts at 100 and loses 50 for every payTo wallet change in 30 days, minus the share of probes where the quoted wallet did not match the catalog. A wallet change in the last 7 days also caps the verdict at Caution.
Listing age5%Days since the endpoint first appeared in any catalog, saturating at 30 days.
HTTPS5%Whether the endpoint is served over HTTPS.

Verdicts

Caps

Some events are serious enough that no amount of good history should produce a Pay verdict until they clear:

Confidence

Each score carries a confidence level based on how much data it rests on: low with fewer than 4 probes in 30 days, medium from 4, and high with at least 12 probes spanning 3 or more days.

Host scores

A host score pools the probes of all its endpoints and applies the same formula, so one dead endpoint among fifty costs little, while a wallet change on any endpoint caps the whole host.

Categories

Every endpoint is assigned one of 23 categories from its listing: the seller's description, the URL path, the service name, tags, the hostname and the field names of the example input the seller published. Ordered rules run first and record which text they matched (a match on the description alone is confidence 0.9; a match that needed the path or metadata is 0.6). Listings the rules cannot place are sent to a small language model with the same category list and a fixed definition of each, and its answer and rationale are stored. Every classification is kept with its method and classifier version; the newest row is the current category and nothing is overwritten. Categories decide which delivery check a paid probe runs; they never change a score.

CategoryWhat it coversDelivery check
Chain readBalances, blocks, gas, logs, ENS, contract calls on a public chain.planned
Crypto priceSpot prices, tickers, candles and market snapshots for crypto assets.planned
Web searchSearch over the web, news or social media.planned
Web scrapeFetch or read a page or profile and return its content, often as markdown.planned
EnrichmentCompany or person lookup and contact enrichment.planned
EmailSend, receive or validate email.planned
DocumentPDF, OCR, transcription and file conversion.planned
UtilityGeocoding, weather, currency, randomness, time, small calculators.planned
Image generationText to image and image editing.planned
InferenceLLM chat completions, embeddings, summarisation, translation and other model output.none (no ground truth)
SignalTrading signals, forecasts, risk verdicts and AI-enriched reports.none (no ground truth)
NoveltyJokes, facts, horoscopes, coin flips.planned
DNS and domainsDNS records, WHOIS/RDAP, TLS certificates, IP intelligence.planned
Data transformHashes, encodings, JSON/CSV tools and other deterministic transforms.planned
ComputationMathematical and scientific computations with a stated formula.planned
Crypto market dataTVL, yields, funding, liquidations, prediction markets, token safety.planned
Finance dataStock quotes, SEC filings, treasury and macro series.planned
Web auditSite, SEO, security-header and dependency audits of a URL you supply.none (no ground truth)
Public dataGovernment and open datasets, transit, jobs, real estate, travel, sports.none (no ground truth)
x402 toolingx402 endpoint checkers, catalog search, payment-header tools.none (no ground truth)
CommercePrepaid credits, tips, faucets, listings and uploads.none (no ground truth)
ComplianceRegulatory checks, sanctions screening, tax and customs calculators.none (no ground truth)
OtherNothing above fits, or the listing says too little to tell.none (no ground truth)

Reasons

Every verdict carries its two most important reasons in plain English: caps first, then the components that cost the most points, or the strongest positives when little was lost.

What we do not measure

Output quality, correctness, latency beyond basic responsiveness, or value for money. A seller that reliably returns garbage for the quoted price can score 100.

Configuration

All weights, thresholds and windows above are read live from a single configuration file in the open-source worker, so this page always matches the code that computes the scores.