Paywary

Leaderboard / http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run / endpoint

POST https://http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run/api/readiness

Scores measure reliability and honesty, not output quality.

94Payconfidence: medium
  • Listed only 2 days ago; new listings earn trust over 30 days.
  • Answered all 10 probes in the last 7 days.
Category
x402 tooling by llm, confidence 60%
Latest quote
$0.006 on Base to 0xb48D…f7a9
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
58m ago
Next probe
2026-11-18 18:18 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
8w 5%
HTTPS
100w 5%

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen
cdpexactBase0x8335…2913$0.0060xb48D…f7a9defaultyes2h 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
36h agox402 tooling60%llmv1claude-haiku-5-5: The endpoint checks whether an API is agent-ready by performing OpenAPI/Swagger discovery and preflight, returning a readiness state. This is a tool for checking x402/agent API endpoints rather than returning chain, market, or business data, so x402_meta fits best, though it could also be read as a web audit of a supplied URL.
40h agoOther40%rulesv1rule none matched "" in none

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
58m agofree402147 msv2yes$0.0060xb48D…f7a9—
7h agofree402149 msv2yes$0.0060xb48D…f7a9—
13h agofree402146 msv2yes$0.0060xb48D…f7a9—
20h agofree402157 msv2yes$0.0060xb48D…f7a9—
27h agofree402159 msv2yes$0.0060xb48D…f7a9—
33h agofree402173 msv2yes$0.0060xb48D…f7a9—
39h agofree402187 msv2yes$0.0060xb48D…f7a9—
45h agofree402146 msv2yes$0.0060xb48D…f7a9—
2d agofree402147 msv2yes$0.0060xb48D…f7a9—
2d agofree402156 msv2yes$0.0060xb48D…f7a9—