10 of 10 routes on responsive originsnostr.halowerk.com
nostr
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 public key is resolved by reading its kind 0 profile from relays and taking the lud16 or lud06 field it publishes.
10
resources
2
data sources
1
network identifiers
21
registry calls / 30d
RESOURCE SAMPLE · 10 OF 10
search all →POST
https://nostr.halowerk.com/follower-graph
https://nostr.halowerk.com/follower-graph
origin + 2 sources
POST
https://nostr.halowerk.com/lnurl-invoice
https://nostr.halowerk.com/lnurl-invoice
origin + 2 sources
POST
https://nostr.halowerk.com/nip05-verify
https://nostr.halowerk.com/nip05-verify
origin + 2 sources
POST
https://nostr.halowerk.com/relay-health
https://nostr.halowerk.com/relay-health
origin + 2 sources
POST
https://nostr.halowerk.com/rss-to-nostr
https://nostr.halowerk.com/rss-to-nostr
origin + 2 sources
POST
https://nostr.halowerk.com/zap-receipt-check
https://nostr.halowerk.com/zap-receipt-check
origin + 2 sources