Paywary

Leaderboard / api.particle.pro / endpoint

GET https://api.particle.pro/v1/podcasts/episodes/search

Scores measure reliability and honesty, not output quality.

31Avoidconfidence: low
  • No response to any of the 3 probes in the last 30 days.
  • Answered 0 of 3 probes in the last 7 days (0%).
Category
Web search by llm, confidence 80%
Latest quote
— on — to —
Uptime
0% / 7d, 0% / 30d
Delivery
none not yet paid-tested
Observed
none reported yet (opt-in wrapper telemetry)
HTTPS
yes
First listed
2026-11-16
Last probe
18h ago
Next probe
2026-11-19 17:33 UTC

Score components

Uptime, 7 days
0w 15%
Uptime, 30 days
0w 15%
Valid x402 challenge
n/aexcluded
Price honesty
n/aexcluded
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.030x59f3…c5f7defaultyes6h 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
21h agoWeb search80%llmv1claude-haiku-5-5: The endpoint searches podcast episode content, which is a search over media content much like news or social search, returning matching episodes. It fits web_search best, though podcast-specific data could arguably fall under public_data or other.
37h agoPublic data60%rulesv1rule public_data matched "podcast" in description

Probe history

WhenKindStatusLatencyx402ValidQuotedPay toFlags
18h agofreenetwork145 ms————no_responsefetch_error:network
42h agofreenetwork201 ms————no_responsefetch_error:network
2d agofreenetwork46 ms————no_responsefetch_error:network