Paywary

Leaderboard / changefeed.dev / endpoint

GET https://changefeed.dev/v1/changes

Scores measure reliability and honesty, not output quality.

94Payconfidence: medium
  • Listed only 2 days ago; new listings earn trust over 30 days.
  • Answered all 11 probes in the last 7 days.
Category
Other by llm, confidence 40%
Latest quote
$0.005 on Base to 0xb2BF…B303
Uptime
100% / 7d, 100% / 30d
Delivery
none not yet paid-tested
Observed
none reported yet (opt-in wrapper telemetry)
HTTPS
yes
First listed
2026-11-16
Last probe
3h ago
Next probe
2026-11-19 01:38 UTC

Score components

Uptime, 7 days
100w 15%
Uptime, 30 days
100w 15%
Valid x402 challenge
100w 15%
Price honesty
100w 15%
Delivery after payment
n/aexcluded
Wallet stability
100w 10%
Listing age
9w 5%
HTTPS
100w 5%

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen
cdpexactBase0x8335…2913$0.0050xb2BF…B303defaultyes5h ago

Paid probes

No paid probes yet. Paid probing is off by default and runs weekly per host under a strict spend cap; each paid probe links to its on-chain transaction here.

Delivery checks

Inside each paid probe we ask for something whose correct answer we know, then compare. A pass means the seller delivered what it was paid for; a fail means it charged and returned something wrong; inconclusive means we could not judge (no reference, unknown input shape, or a non-2xx response). Every row carries the request, the response hash and the reference so the verdict can be reproduced. Judged results feed the "Delivery after payment" component (pass 1, error after payment 0.25, fail 0); inconclusive rows are excluded; a fail in the last 14 days caps the verdict at caution. Methodology.

No delivery checks yet. They run inside the weekly paid probe.

Classification history

Every classification is kept; the newest row is the current category. Rules match the listing text; the model is consulted only when the rules are unsure.

WhenCategoryConfidenceMethodVersionEvidence
39h agoOther40%llmv1claude-haiku-5-5: Returns recent normalized change notices (breaking, deprecation, security, release) for tracked APIs/SDKs. No listed category covers developer changelog or release-monitoring feeds, and none of the closest fits (web_search, web_scrape, signal) match the change-feed nature well, so it falls to other with moderate-low confidence.
2d agoOther40%rulesv1rule none matched "" in none

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
3h agofree40271 msv2yes$0.0050xb2BF…B303—
10h agofree402665 msv2yes$0.0050xb2BF…B303—
16h agofree402824 msv2yes$0.0050xb2BF…B303—
23h agofree402622 msv2yes$0.0050xb2BF…B303—
29h agofree402698 msv2yes$0.0050xb2BF…B303—
36h agofree402824 msv2yes$0.0050xb2BF…B303—
42h agofree402846 msv2yes$0.0050xb2BF…B303—
2d agofree402539 msv2yes$0.0050xb2BF…B303—
2d agofree402459 msv2yes$0.0050xb2BF…B303—
3d agofree402481 msv2yes$0.0050xb2BF…B303—
3d agofree402602 msv2yes$0.0050xb2BF…B303—