Classify a Nostr pubkey as likely_human, suspicious, or likely_spam using multi-signal analysis. 2 sats per request.
| Time | Status | HTTP | Latency | Error |
|---|---|---|---|---|
| 2026-03-20 16:58:10 | down | 530 | 32ms | HTTP 530 |
| 2026-03-20 16:24:52 | down | 530 | 37ms | HTTP 530 |
| 2026-03-20 15:52:23 | down | 530 | 31ms | HTTP 530 |
| 2026-03-20 15:31:03 | down | 530 | 30ms | HTTP 530 |
| 2026-03-20 14:57:26 | down | 530 | 44ms | HTTP 530 |
| 2026-03-20 14:10:08 | down | 530 | 80ms | HTTP 530 |
| 2026-03-20 13:01:24 | down | 530 | 48ms | HTTP 530 |
| 2026-03-20 12:03:36 | down | 530 | 31ms | HTTP 530 |
| 2026-03-20 10:57:19 | down | 530 | 33ms | HTTP 530 |
| 2026-03-20 09:59:40 | down | 530 | 28ms | HTTP 530 |
| 2026-03-20 08:51:06 | down | 530 | 31ms | HTTP 530 |
| 2026-03-20 08:05:01 | down | 530 | 28ms | HTTP 530 |
| 2026-03-20 06:56:35 | down | 530 | 31ms | HTTP 530 |
| 2026-03-20 05:55:20 | down | 530 | 31ms | HTTP 530 |
| 2026-03-20 05:03:49 | down | 530 | 32ms | HTTP 530 |
| 2026-03-20 03:53:19 | down | 530 | 26ms | HTTP 530 |
| 2026-03-20 02:59:44 | down | 530 | 27ms | HTTP 530 |
| 2026-03-20 02:04:12 | down | 530 | 26ms | HTTP 530 |
| 2026-03-20 00:35:34 | down | 530 | 29ms | HTTP 530 |
| 2026-03-19 23:52:19 | down | 530 | 24ms | HTTP 530 |