Leaderboard / pkgpulse.letom1176.workers.dev / endpoint
GET https://pkgpulse.letom1176.workers.dev/api/pick
Scores measure reliability and honesty, not output quality.
- Listed only 2 days ago; new listings earn trust over 30 days.
- Answered all 9 probes in the last 7 days.
- Category
- Web audit by llm, confidence 50%
- Latest quote
- $0.015 on Base to 0xc863…2bc2
- 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
- 5h ago
- Next probe
- 2026-11-18 11:55 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.015 | 0xc863…2bc2 | default | yes | 6h 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.
| When | Category | Confidence | Method | Version | Evidence |
|---|---|---|---|---|---|
| 34h ago | Web audit | 50% | llm | v1 | claude-haiku-5-5: The endpoint produces npm package health reports and ranks dependencies, which is closest to auditing software dependencies, but it is not a URL audit and no listed category covers package health comparisons directly. Dependency audits fit web_audit best among the options, though confidence is moderate. |
| 37h ago | Public data | 60% | rules | v1 | rule public_data matched "npm package" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 5h ago | free | 402 | 324 ms | v2 | yes | $0.015 | 0xc863…2bc2 | — |
| 11h ago | free | 402 | 919 ms | v2 | yes | $0.015 | 0xc863…2bc2 | — |
| 18h ago | free | 402 | 383 ms | v2 | yes | $0.015 | 0xc863…2bc2 | — |
| 24h ago | free | 402 | 846 ms | v2 | yes | $0.015 | 0xc863…2bc2 | — |
| 30h ago | free | 402 | 347 ms | v2 | yes | $0.015 | 0xc863…2bc2 | — |
| 37h ago | free | 402 | 311 ms | v2 | yes | $0.015 | 0xc863…2bc2 | — |
| 43h ago | free | 402 | 782 ms | v2 | yes | $0.015 | 0xc863…2bc2 | — |
| 2d ago | free | 402 | 81 ms | v2 | yes | $0.015 | 0xc863…2bc2 | — |
| 2d ago | free | 402 | 315 ms | v2 | yes | $0.015 | 0xc863…2bc2 | — |