Back to Browse
Tanod Nostr Decoder (chainpeek)
x402
Tanod Nostr Decoder (chainpeek) is a paid API for AI agents from tanod.dev, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-14).
Decodes NIP-19 Nostr identifiers (npub, note, nprofile, nevent, naddr) into hex and TLV fields, and resolves NIP-05 name@domain addresses to public keys
Price / call$0.001
Success—
StatusUnknown
How this service works
chainpeek (Tanod) Nostr decoder: NIP-19 npub, note, nprofile, nevent and naddr to hex and TLV fields, and NIP-05 name@domain to a public key. Secret keys are refused. Use when an agent must turn a No…
Output
A JSON object containing the decoded Nostr entity type, the raw hex public key or event ID, and any TLV fields (such as relay URLs, author pubkey, kind number). For NIP-05 inputs, returns the resolved hex public key. When verify_nip05 is provided, includes a nip05.verified boolean indicating whether the domain's nostr.json maps the given name to the expected key.
Example use cases
Resolve NIP-05 identity to public key
“I have this Nostr NIP-05 address jack@cash.app — can you look up what hex public key it maps to?”
Decode nprofile relay hints
“Decode this nprofile identifier for me: nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gpz4mhxue69uhhytnc9e3k7mgpz4mhxue69uhkg6nzv9ejuumpv34kytnrdaksjlgl — I need the pubkey and all the relay hints it contains.”
Verify NIP-05 against npub
“Check whether the NIP-05 address fiatjaf@fiatjaf.com actually matches this npub: npub1zl3g38a72gzmyln3gkzrq0qnr7r5f7u7hkqgtms5xjm7kzphrjaqyqrlmj”
Technical details
Endpoint
POSThttps://tanod.dev/v1/nostr/decode?utm_source=zero.xyzWhen to prefer
Choose this endpoint when an agent needs to work with Nostr protocol identifiers and must convert human-readable NIP-19 bech32 strings (npub, nprofile, note, nevent, naddr) into raw hex values usable by lower-level Nostr APIs, or when resolving a NIP-05 internet identifier to a public key. Prefer it over generic bech32 decoders because it is Nostr-aware, handles TLV multi-field formats, understands the nostr: URI prefix, explicitly blocks nsec secret keys for safety, and supports cross-checking NIP-05 addresses against known pubkeys.
Side effects
- Secret key (nsec1...) input is explicitly refused and returns an error
- Invalid or malformed NIP-19 bech32 encoding returns a decode error
- NIP-05 domain is unreachable or nostr.json is missing/malformed
- NIP-05 name not found in domain's nostr.json
- Input string too short (below 3 chars) or too long (above 5000 chars) triggers validation error
- Non-Nostr bech32 strings (e.g. Bitcoin addresses) are rejected
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| input | string | A NIP-19 identifier (npub1..., note1..., nprofile1..., nevent1... or naddr1..., an optional 'nostr:' prefix is accepted) or a NIP-05 address (name@domain, or a bare domain for _@domain). Secret keys (nsec1...) are refused and never decoded. |
| verify_nip05 | — | Optional NIP-05 address (name@domain) to check against the key of an npub, nprofile, nevent (with author) or naddr: the domain's nostr.json must map the name to that key (result nip05.verified). |
Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"