Paywary

Leaderboard / api.x402card.org / endpoint

POST https://api.x402card.org/api/esim/purchase

Scores measure reliability and honesty, not output quality.

82Payconfidence: medium
  • Answered 8 of 9 probes in the last 7 days (89%).
  • Answered 8 of 9 probes in the last 30 days (89%).
Category
Other by llm, confidence 10%
Latest quote
— on — to —
Uptime
89% / 7d, 89% / 30d
Delivery
none not yet paid-tested
Observed
none reported yet (opt-in wrapper telemetry)
HTTPS
yes
First listed
2026-11-16
Last probe
50m ago
Next probe
2026-11-18 12:09 UTC

Score components

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

Catalog listings

SourceSchemeNetworkAssetListed pricePay toFlowCurrentLast seen

Listing changes

WhenEventFromTo
2h agodisappeared——

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
2h agoOther10%llmv1claude-haiku-5-5: Endpoint path suggests an eSIM purchase, but no description, tags or fields are given, so the category is unclear.
2h agoCommerce50%rulesv1rule commerce matched "/purchase" in metadata
30h agoCommerce75%llmv1claude-haiku-5-5: The endpoint sells a prepaid travel eSIM plan and returns its installation QR and activation data. That is a purchase/listing of a prepaid product, which fits commerce best. It is not public_data or utility, though the connectivity tags could suggest telecom, so confidence is moderate-high rather than certain.
33h agoPublic data60%rulesv1rule public_data matched "travel" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
50m agofree502819 ms—no——server_errorstatus_not_402
7h agofree402695 msv2yes$0.470x4d5D…02E9—
14h agofree4021077 msv2yes$0.470x4d5D…02E9—
20h agofree4022174 msv2yes$0.470x4d5D…02E9—
27h agofree402774 msv2yes$0.470x4d5D…02E9—
33h agofree402596 msv2yes$0.470x4d5D…02E9—
39h agofree402890 msv2yes$0.470x4d5D…02E9—
45h agofree402632 msv2yes$0.470x4d5D…02E9—
2d agofree402837 msv2yes$0.470x4d5D…02E9—