nostr.halowerk.com
nostr.halowerk.com · 10 paid endpoints · listed 2026-10-27
Fetches kind 3 contact lists over up to twelve relays. Because kind 3 is replaceable, several relays regularly hold different versions; only the one with the highest created_at is used and the answer states which relays carried that version and how many older versions were seen, so a stale relay never quietly overwrites a current list. At depth 1 the answer is the account and its outgoing follows.
Paid endpoints
| Method | Endpoint | Price | Networks |
|---|---|---|---|
| POST | nostr.halowerk.com/event-sign Three modes over the same event structure. In preimage mode the caller supplies a public key and the event fields; the answer holds the exact NIP-01 serialisati | $0.001 | Base |
| POST | nostr.halowerk.com/key-convert Takes any public NIP-19 identifier or a 64-character hex value and returns every representation it can be expressed as. A decoded nprofile or nevent yields not | $0.001 | Base |
| POST | nostr.halowerk.com/nip05-verify Fetches https://domain/.well-known/nostr.json with the name query parameter and reads the mapping the domain publishes. The answer states the resolved public ke | $0.001 | Base |
| POST | nostr.halowerk.com/lnurl-invoice Accepts three forms of recipient. A bech32 lnurl is decoded to its callback URL, a Lightning address is resolved through the well-known lnurlp path, and a Nostr | $0.002 | Base |
| POST | nostr.halowerk.com/rss-to-nostr Fetches the feed over https with redirect and size limits, recognises RSS 2.0, RDF and Atom, and converts each entry into a NIP-01 event. Kind 1 produces a shor | $0.002 | Base |
| POST | nostr.halowerk.com/zap-receipt-check Takes a kind 9735 receipt directly or fetches it from relays by event id, then runs eight named checks and reports each one separately with its reason. The rece | $0.002 | Base |
| POST | nostr.halowerk.com/relay-health Every relay is measured twice over. Over WebSocket a genuine REQ query is sent and the connection time, the time to end of stored events and the number of event | $0.003 | Base |
| POST | nostr.halowerk.com/bot-score Fetches the recent notes of one public key across several relays and measures six independent signals: posting rate per day, the coefficient of variation of the | $0.004 | Base |
| POST | nostr.halowerk.com/follower-graph Fetches kind 3 contact lists over up to twelve relays. Because kind 3 is replaceable, several relays regularly hold different versions; only the one with the hi | $0.004 | Base |
| POST | nostr.halowerk.com/zap-radar Collects kind 9735 zap receipts addressed to one public key over up to twelve relays, merges them by event id and reports who sent how much over the requested w | $0.004 | Base |
Latest checks
| When | Endpoint | HTTP | ms | Result |
|---|---|---|---|---|
| 5 days ago | nostr.halowerk.com/bot-score | 402 | 192 | valid x402 v2 terms |
Income on Base (7 days)
This provider's payout address is shared by several providers, so its income is not shown as its own.
Is this your API?
<a href="https://logicnodes.io/observatory/p/nostr.halowerk.com"><img src="https://logicnodes.io/observatory/badge/nostr.halowerk.com.svg" alt="x402 status"></a>
Claim it for free with
x402_provider_claim (sign with your payout address), and get an alert within minutes when it stops answering with x402_monitor_create ($5 for 30 days). Both work over MCP (https://logicnodes.io/mcp/v2) or POST https://logicnodes.io/v1/tools/<tool>.Income is all USDC received by the provider's payout address on Base, whatever the source. Score: 0-100: 50 x share of checks in the last 72 h that returned valid x402 payment terms + 30 x min(1, log10(1 + USDC received in 7 days) / 4) + 20 x min(1, log10(1 + distinct payers in 7 days) / 3). A provider never checked scores on income only; income is all USDC received by its payout address on Base, whatever the source. JSON: /v1/observatory/providers/nostr.halowerk.com