Leaderboard / x402-v2-mint-npm-search.vercel.app / endpoint
POST https://x402-v2-mint-npm-search.vercel.app/v1/npm-search
Scores measure reliability and honesty, not output quality.
- Listed only 1 day ago; new listings earn trust over 30 days.
- Answered all 7 probes in the last 7 days.
- Category
- Web search by llm, confidence 80%
- Latest quote
- $0.003 on Base to 0xc22f…Ef69
- Uptime
- 100% / 7d, 100% / 30d
- Delivery
- none not yet paid-tested
- HTTPS
- yes
- First listed
- 2026-11-16
- Last probe
- 2h ago
- Next probe
- 2026-11-18 00:07 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.003 | 0xc22f…Ef69 | default | yes | 43m 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 |
|---|---|---|---|---|---|
| 6h ago | Web search | 80% | llm | v1 | claude-haiku-5-5: The endpoint searches the npm package registry by text query and returns matching packages with names, versions, descriptions and download counts. That is a search over a public index, so web_search fits best, though it is a package registry rather than the open web. |
| 23h ago | Public data | 60% | rules | v1 | rule public_data matched "npm registry" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 2h ago | free | 402 | 154 ms | v2 | yes | $0.003 | 0xc22f…Ef69 | — |
| 9h ago | free | 402 | 121 ms | v2 | yes | $0.003 | 0xc22f…Ef69 | — |
| 15h ago | free | 402 | 153 ms | v2 | yes | $0.003 | 0xc22f…Ef69 | — |
| 21h ago | free | 402 | 155 ms | v2 | yes | $0.003 | 0xc22f…Ef69 | — |
| 27h ago | free | 402 | 118 ms | v2 | yes | $0.003 | 0xc22f…Ef69 | — |
| 34h ago | free | 402 | 136 ms | v2 | yes | $0.003 | 0xc22f…Ef69 | — |
| 40h ago | free | 402 | 146 ms | v2 | yes | $0.003 | 0xc22f…Ef69 | — |