HALOWERKNostrwerk
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 key in hex and as npub, the relay hints the document lists for that key, and the HTTP status and final URL after redirects, so a redirect to a login page is distinguishable from a genuine answer.
POST https://nostr.halowerk.com/nip05-verifyEingaben
| Feld | Typ | Pflicht | Beschreibung |
|---|---|---|---|
| identifier | string | Ja | NIP-05 identifier as name@domain, or a bare domain for the root identifier _@domain. |
| expect_pubkey | string | Nein | Public key as hex, npub or nprofile that the domain is expected to confirm. |
Vollständiges Eingabeschema anzeigen
{
"type": "object",
"required": [
"identifier"
],
"additionalProperties": false,
"properties": {
"identifier": {
"type": "string",
"description": "NIP-05 identifier as name@domain, or a bare domain for the root identifier _@domain."
},
"expect_pubkey": {
"type": "string",
"description": "Public key as hex, npub or nprofile that the domain is expected to confirm."
}
}
}Veröffentlichtes Eingabebeispiel
{
"identifier": "beispiel"
}Ergebnis & Dokumentation
Maschinenlesbare Dokumentation dieses Hubs
Quelle dieser Seite: der veröffentlichte HALOWERK-Katalog. Stand: 2026-11-01, 15:19 UTC.
Weitere Endpunkte dieses Hubs
- Nostrwerk0,004 USDC
bot score
POSThttps://nostr.halowerk.com/bot-scoreFetches 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 intervals between posts, how many of those intervals sit within a few seconds o
- Nostrwerk0,001 USDC
event sign
POSThttps://nostr.halowerk.com/event-signThree 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 serialisation, the SHA-256 event id derived from it and the 32 bytes to sign, so the caller
- Nostrwerk0,004 USDC
follower graph
POSThttps://nostr.halowerk.com/follower-graphFetches 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