Leaderboard / api.pulsewatch.us / endpoint
GET https://api.pulsewatch.us/v1/status
Scores measure reliability and honesty, not output quality.
- Listed only 3 days ago; new listings earn trust over 30 days.
- Answered all 12 probes in the last 7 days.
- Category
- Other by llm, confidence 45%
- Latest quote
- $0.01 on Base to 0x2dAF…65dD
- 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
- 4h ago
- Next probe
- 2026-11-19 07:50 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| payai | exact | Base | 0x8335…2913 | $0.01 | 0x2dAF…65dD | default | yes | 6h ago |
| cdp | exact | Base | 0x8335…2913 | $0.01 | 0x2dAF…65dD | default | yes | 6m 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 |
|---|---|---|---|---|---|
| 2d ago | Other | 45% | llm | v1 | claude-haiku-5-5: Returns live outage status and incident summaries for SaaS vendors, which is monitoring-style data not covered by a specific category. Closest fits are signal or public_data, but neither matches well, so it falls to other with moderate confidence. |
| 2d ago | Other | 40% | rules | v1 | rule none matched "" in none |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 4h ago | free | 402 | 607 ms | v2 | yes | $0.01 | 0x2dAF…65dD | — |
| 11h ago | free | 402 | 346 ms | v2 | yes | $0.01 | 0x2dAF…65dD | — |
| 18h ago | free | 402 | 12 ms | v2 | yes | $0.01 | 0x2dAF…65dD | — |
| 24h ago | free | 402 | 572 ms | v2 | yes | $0.01 | 0x2dAF…65dD | — |
| 31h ago | free | 402 | 796 ms | v2 | yes | $0.01 | 0x2dAF…65dD | — |
| 37h ago | free | 402 | 441 ms | v2 | yes | $0.01 | 0x2dAF…65dD | — |
| 44h ago | free | 402 | 525 ms | v2 | yes | $0.01 | 0x2dAF…65dD | — |
| 2d ago | free | 402 | 302 ms | v2 | yes | $0.01 | 0x2dAF…65dD | — |
| 2d ago | free | 402 | 369 ms | v2 | yes | $0.01 | 0x2dAF…65dD | — |
| 3d ago | free | 402 | 178 ms | v2 | yes | $0.01 | 0x2dAF…65dD | — |
| 3d ago | free | 402 | 601 ms | v2 | yes | $0.01 | 0x2dAF…65dD | — |
| 3d ago | free | 402 | 686 ms | v2 | yes | $0.01 | 0x2dAF…65dD | — |