# Tanod Nostr Decoder (chainpeek)

> 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

## Facts

- Endpoint: POST https://tanod.dev/v1/nostr/decode?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tanod-nostr-decoder-chainpeek-ad43e7e4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6UyrKZqUAvv5eh9pj218P

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability tanod-nostr-decoder-chainpeek-ad43e7e4 -d '<json body>'
```

Example prompt: Can you decode this Nostr identifier npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl4xcrectabvs6j85rz to its raw hex public key?

## When to prefer this

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.

## Known failure modes

- 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

## 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.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "string",
   "maxLength": 5000,
   "minLength": 3,
   "description": "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": {
   "anyOf": [
    {
     "type": "string",
     "maxLength": 320,
     "minLength": 3
    },
    {
     "type": "null"
    }
   ],
   "default": null,
   "description": "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)."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tanod-nostr-decoder-chainpeek-ad43e7e4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from tanod.dev](https://www.zero.xyz/host/tanod.dev/llms.txt)