Nostr Public Notes Monitor - Verified Relay Watchlists

SOURCE COVERAGE & PRACTICAL LIMITS

Full product guide

Documentation captured from build 1.0.5. Example outputs retain their original sample context; they are not live results.

Open this Actor in Console · Try a small run · Cost

Mayd-It · Verified public notes

Collect a bounded watchlist of public Nostr notes with signed text and relay provenance. Filter explicit author keys or hashtag tags, deduplicate observations across two relays, and optionally skip notes already saved.

Source scope: Public kind 1 notes from relay.damus.io and nos.lol. Signatures are verified; verification establishes the signing key, not a person’s identity or a post’s truth.

What you get

• Distinct note IDs with original signed content and verified signatures.
• Author, tag, time and literal keyword filters with observed relay provenance.
• Saved-history deduplication for recurring collection without a WebSocket client.

Try a small run

Copy this exact input into the Actor’s JSON input editor, then run it.

{
  "relays": [
    "wss://relay.damus.io",
    "wss://nos.lol"
  ],
  "perRelayLimit": 10,
  "maxResults": 20,
  "hashtags": [
    "nostr"
  ]
}

This example requests a ten-event window per relay and saves at most 20 distinct matching notes tagged nostr. No account or API key is required. {} uses the same tag and a seven-day lookback; set your own filters for a watchlist, or explicitly pass "hashtags": [] for an unfiltered recent window. Open the dataset for verified rows and SUMMARY for accepted, rejected and incomplete-source counts.

Understand your run

Open Run report in the run’s Output tab for saved-record counts, reported source issues and limits, and suggested next steps. Use CSV export to take the saved results into a spreadsheet. The existing JSON results and detailed machine-readable summary remain available.

The report reflects this run’s recorded coverage. A successful run or a saved result does not establish that every possible source record was collected.

Cost

FREE / BRONZE: $0.002 per saved observation ($2 per 1,000). SILVER: $1.60 per 1,000. GOLD / PLATINUM / DIAMOND: $1.20 per 1,000.

The Actor Start event is $0.00005 per charged start unit, with one unit per GB of Actor memory and a minimum of one. The Pricing tab shows the rate for your Apify tier. New, changed and ordinarily saved unchanged observations use the same result rate. Skipped unchanged rows, rejected events, duplicates and error diagnostics are not paid result rows. Use onlyChanges for repeated monitoring after establishing history.

A real result

Selected fields from a recorded run on 10 October 2026. This is an example of the output shape; source content and counters can change.

{
  "id": "19befb884f45b68a482cde7cc5a47c4049fba50e0ff97001fa303c9bc6222d60",
  "kind": 1,
  "createdAt": "2026-10-10T23:14:02.000Z",
  "hashtags": [
    "bitcoin",
    "moscowtime",
    "nostr"
  ],
  "sourceRelays": [
    "wss://nos.lol"
  ],
  "signatureVerified": true
}

This retained sample came from the one-relay community example below. The complete row also includes signed content, its author public key and signature. Relay provenance records where the Actor observed the note.

More examples

Public Nostr Bitcoin Hashtag Notes

Request notes with the exact, case-sensitive bitcoin tag.

{
  "hashtags": [
    "bitcoin"
  ],
  "perRelayLimit": 10,
  "maxResults": 20
}

Nostr Community Tag on nos.lol

Use just nos.lol for the exact nostr tag, with at most ten saved notes.

{
  "relays": [
    "wss://nos.lol"
  ],
  "hashtags": [
    "nostr"
  ],
  "perRelayLimit": 10,
  "maxResults": 10
}

This is an experimental market with limited observed Apify demand; no audience-growth or revenue promise is implied. Every event ID is recomputed and its Schnorr signature is checked before a paid row is saved.

Input and coverage

Author, hashtag, keyword and time groups combine with AND. All filters are checked locally even when sent to a relay. Notes are sorted newest first, then by event ID for ties. Public text can include spam, empty text, links and arbitrary content. Media and linked pages are not fetched, and keyword matching does not infer sentiment or identity.

The Actor waits for EOSE, the relay's acknowledgement that its stored-event response has ended. Missing EOSE, refusals and source errors are recorded as partial or failed coverage. Unsupported, oversized, malformed or unverifiable events are always excluded from output and billing. A completed response with usable verified notes may succeed despite these exclusions, with a warning and categorized rejection counts. If every received event from a source is rejected, that source is marked unusable. Rejected content is never retained; diagnostics contain only the event ID when validly shaped and a reason code.

EOSE completes only the requested bounded response, including processing and rejecting unsupported events. It does not establish all matching history, all public Nostr activity, acceptance of every received event, or the absence of deleted notes. The Actor never publishes events, signs in, authenticates to paid relays, reads private messages, or enriches profiles. Public DNS is checked and pinned for TLS connections; redirects are not followed.

A temporary HTTP 502, 503 or 504 handshake response gets at most one retry after a 500 ms pause, within the original relay time allowance. The attempt outcomes remain in SUMMARY.sourceCoverage. Authentication, access restrictions, redirects, subscription refusals and protocol errors are not retried.

Each message is capped at 128 KiB, each relay response at 4 MiB, and each content field at 64,000 UTF-8 bytes. Up to 500 tags are accepted per event. Oversized or unverifiable notes are not billed. These limits are deliberately smaller than some relay limits and are reported in SUMMARY if encountered.

Results

One dataset row represents one distinct verified note in this run:

SUMMARY includes rowsSaved, rowsObserved (distinct matching candidates considered for output), verifiedMatchingNotes, unchangedSkipped, sourcesSucceeded, sourceCoverage, invalidEvents, rejectionsByReason, filtered, failedSources, windowComplete, limits and status. invalidEvents counts every validation exclusion, including validly signed events exceeding supported size limits; it is not a count of forged signatures. Each source includes reason counts and at most 20 {id, reason} rejection samples. windowComplete describes transport and verification processing, not acceptance of all received events. Source counters are not audience or engagement metrics. A healthy empty query or unchanged repeat warns and succeeds. A zero-output operational failure fails the run. A zero-row spending-limit stop is a normal budget outcome.

Saved history

Set comparePrevious: true or onlyChanges: true, and choose a snapshotName. The first comparison run warns and returns matching notes as new. History is stored in the named nostr-public-notes-monitor-history key-value store and separated by relay, filter and time-window configuration.

Only confirmed saved rows advance their own history. Positive observations from a partial relay response may be saved and remembered, with the run explicitly marked partial; this never establishes completeness or deletions. Unchanged repeats are skipped with onlyChanges. Since signed kind 1 event content is immutable, the same valid ID normally remains unchanged. Relay provenance changes do not create false content changes. No automatic deletions are emitted.

For a repeatable historical comparison, use the same fixed since/until, filters and perRelayLimit, and make maxResults large enough for the whole bounded window. Otherwise later runs may find previously unsaved notes. Relay retention and late-arriving events can also change the observed window.

Use one writer per exact history scope. The Actor checks the stored value again before replacing it and refuses an observed conflicting change; the key-value store offers no atomic compare-and-swap, so this is not a distributed lock. Malformed history is preserved with a diagnostic; use a new snapshotName to begin a fresh scope. At 20,000 remembered IDs, choose a new name or narrower watchlist. Named storage and data retention are under your Apify account's control.

Troubleshooting and support

For help, open an Actor issue or contact bmay@mayd-it.com. Include the run ID, selected sources and the relevant SUMMARY message. Do not send credentials. This Actor is independent of the platform.

Content remains subject to its creators’ rights and applicable law. Use public data for a legitimate purpose, honor deletion requests and avoid attempting to identify anonymous authors. Storage charges follow your Apify plan.

Protocol references: NIP-01 events and subscriptions, NIP-10 marked reply references, NIP-11 relay information, nostr-tools. Relay operation, retention and access policies may change; requests that require authentication or are refused are not bypassed.