Substack Publication, Post & Comment Monitor
Pricing
from $0.53 / 1,000 post results
Discover public Substack publications and posts, export publication, author, post and public-comment rows, and monitor compatible snapshots without AI interpretation.
Choose the buyer job first. It controls which target field is required, which source pages are opened, and which result types can be returned.
Required only for topic discovery. Enter up to 10 topics; each creates a separate target and its own coverage receipt. Ignored by the other workflows.
Required only for Publication archive. Paste up to 1,000 Substack URLs, subdomains, or public custom domains. Each becomes a canonical HTTPS target with its own coverage receipt.
Required for Exact posts and Public comments. Paste up to 10,000 canonical public /p/ post URLs and keep maxPosts at least as high as the target count. Comment collection opens only public comment data linked to these posts.
Global ceiling for publication rows, including contextual publication rows linked to exact posts. Raise it with large exact-post batches; reaching it produces CAPPED coverage, never false completeness.
Global ceiling for post rows across all targets. For Exact posts or Public comments it must cover every supplied post URL. A small value is the fastest useful first run; reaching the ceiling produces CAPPED coverage when more posts may exist.
Used only when comments are requested. Limits public comments and replies for each post; a visible next page or cursor makes that comment target CAPPED.
Global comment and reply ceiling across the run. Comment rows add source work and use their own result event when pricing is active.
Optional inclusive YYYY-MM-DD filter for post publication time. This can turn source-complete traversal into FILTERED coverage for the requested result set.
Optional inclusive YYYY-MM-DD filter. It must not be earlier than Published on or after.
Leave empty for every source-exposed type. Selecting values filters normalized posts; an unknown source type remains explicit rather than guessed.
Filters by what the public source actually exposed. Paywalled unavailable means metadata or preview may be public while the paid body remains unavailable.
Keeps posts whose source-exposed reactions + comments + restacks meet this total. It is a deterministic numeric filter, not a quality or trend score.
Current returns normalized rows. Changes seeds the first compatible run without a NEW flood, then emits deterministic title, body-access, rank, and public-metric changes on sequential repeats.
Optional human label included in the state scope. Use a stable label when you intentionally maintain separate monitors over otherwise identical inputs.
Used only in Changes mode. Returns free UNCHANGED change rows for auditing; they do not become paid change events.
Used only for Changes. Leave empty to match the requested publication + post + comment scope automatically, or set an explicit ceiling up to 40,000. Contextual author rows do not create disappearance events.
Opens or parses post detail where needed and returns clean public HTML/text. Exact posts enable this automatically. Paid or private body text is never requested or reconstructed.
Returns normalized publication metadata linked to delivered posts when the public source exposes it.
Returns public author/byline rows. It does not infer private email addresses or subscriber identities.
Requests public comment/reply rows for delivered posts. Public comments workflow enables this automatically; unavailable or unverified comment access is PARTIAL, not empty.
Adds a bounded rawSource object for debugging. Leave off for clean JSON/CSV/Excel rows; internal upload/transcoding keys are not promoted into the default schema.
Fail before source work when the projected current pricing vector could exceed this ceiling. This is the buyer-charge guard, not an infrastructure-cost estimate.
Internal source-request guard sized for the declared exact-target workload. This is a ceiling, not a request target; small row defaults still stop early.
Internal cumulative response-byte guard for deliberate bulk work. This ceiling does not make a small run fetch extra data.
Internal serialized-state guard sized for the declared 40,000-entity maximum.
Internal source-work runtime guard for deliberate bulk runs; ordinary small runs return as soon as their requested scope is complete.
Internal per-request timeout.
Internal bounded retry policy.
Internal fair-access pacing in milliseconds.
