Nostr scraper: profiles, notes, followers and following

Scrape public Nostr data straight from open relays. Give it an account or a keyword and get back clean, structured rows: display name, bio, NIP-05 identifier, Lightning address, website, and recent notes. No login, no API key, no captcha, no proxy required.

Nostr profiles carry contact-grade fields that most social networks hide. The Lightning address (lud16) and NIP-05 identifier are public by design, so a single run can turn one account's social graph into a usable lead list for Bitcoin, Lightning and web3 outreach.

What it does

Five modes, one actor:

• Following: give an account, get every account it follows, resolved to full profiles. This is the fast way to build a lead list from a well-connected hub.
• Followers: give an account, get the accounts that follow it, resolved to full profiles.
• Profiles: look up one or many accounts and get their full metadata.
• Posts: pull recent notes for the accounts you list.
• Search: find notes matching a keyword across search relays, with the author's profile attached.

You can point it at an npub, an nprofile, a raw hex public key, or a NIP-05 address like odell@primal.net. Mixed lists are fine.

Example input

Build a lead list from an account's follow graph:

{
  "mode": "following",
  "identifiers": ["npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx"],
  "maxItems": 100
}

Search notes by keyword:

{
  "mode": "search",
  "searchQuery": "bitcoin lightning",
  "maxItems": 50
}

Look up specific profiles:

{
  "mode": "profile",
  "identifiers": ["odell@primal.net", "npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx"]
}

Output

Profile rows include the npub, hex public key, name, display name, NIP-05, Lightning address, website, bio, avatar and banner, plus a profileUrl you can open in any browser. Note rows include the note text, note id, author, hashtags, timestamp and a noteUrl. Every row has a type (profile or note) and the mode that produced it.

Sample profile row:

{
  "type": "profile",
  "mode": "following",
  "npub": "npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx",
  "name": "ODELL",
  "nip05": "odell@primal.net",
  "lightningAddress": "odell@primal.net",
  "website": "https://odell.xyz",
  "about": "partner - ten31 ...",
  "profileUrl": "https://njump.me/odell@primal.net"
}

Export to JSON, CSV, or Excel, or pull it through the Apify API.

Who uses it

• Bitcoin and Lightning teams building outreach lists with public Lightning addresses.
• Web3 CRM and airdrop research that needs npubs, NIP-05 identifiers and linked sites.
• Analysts tracking how a topic or account grows across the network.
• Client and bot builders who want bulk profile and note data without running their own relay.

How it works

The actor speaks the Nostr protocol (NIP-01) directly to a pool of open relays, queries several at once, and dedupes events by id so you get the most complete result. Keyword search uses NIP-50 search relays. NIP-05 addresses resolve over HTTPS from each domain's /.well-known/nostr.json. All of this is public data that relays serve without authentication.

Notes

Nostr data is spread across relays, so coverage depends on which relays hold a given account's events. The defaults cover the busy public relays; you can override them with the relays field. Search depends on relays that support NIP-50, which come and go, so results there vary more than profile and follow lookups.