Skip to content
Start for freeDashboard

Output format

Output is compact and deterministic, built for an agent’s context window: no colours, no emoji, no padding.

  • The first line is a heading that names the object; the second is a metadata line separated by ·.
  • Engagement is one line with short labels and compact numbers, only the counts the platform provides: likes 1.2K · reposts 88 · replies 64 · quotes 12 · views 210K.
  • Text is verbatim: full long posts and original line breaks, never summarised.
  • Media are single lines: [image] https://… (alt: "…"), or [video 1:42] transcript available: scrollhound transcript ….
  • A quoted post is an inline blockquote, one level deep.
  • An empty result is the single line No results. (exit code 0).
# Thread by Marc Lou (@marc_louvion) · 142K followers
https://x.com/marc_louvion/status/1849000000000000000 · 2026-10-21 14:03 UTC · 3 posts
## 1/3 · likes 1.2K · reposts 88 · replies 64 · quotes 12 · views 210K
I shipped 3 products in 30 days. Here's the exact posting routine:
[image] https://pbs.twimg.com/media/abc.jpg (alt: "Revenue chart")
## Top replies (20 of 64)
- @tibo_maker (98K followers) · likes 220 · 2026-10-21: The "post the build" point is underrated.
next: scrollhound x replies 1849000000000000000 --cursor eyJ2IjoxLCJwIjoidHdpdHRlcmFwaS1pbyJ9

(An illustrative example of the format, not a real thread.)

When there’s more, the last line is next: followed by the exact command to run, with a --cursor. Lists page this way. Long transcripts and Articles (over about 20,000 characters) are split into chunks the same way, and every chunk after the first is a free re-read.

Big lists (say x posts --limit 500) stop at about 20,000 characters with a line like showing 1–47 of 500 posts to keep this readable; next: shows #48 onward. Following next: continues from post 48 without fetching again, so it’s free. Long comment trees say how many comments they show. --json always returns everything that was fetched.

--limit is how many items to fetch at least: X returns replies, quotes and search results in whole pages, so you can get a few more than you asked for (for example 73 replies for --limit 50).

Comments and replies are only fetched when asked for (--comments <n>). A post read without them ends with a line like 318 comments on Reddit, not loaded (ask for comments to include them).

Add --json to any command:

{
"data": { "kind": "thread", "posts": [], "replies": { "items": [], "nextCursor": null } },
"meta": { "requestId": "…", "cached": true, "notionalCredits": 0, "warnings": [] }
}

data uses the same shape whichever platform it came from: post, thread, article, user, video, hn_item, trends, subreddit, reddit_thread and the paged lists. meta.cached is true for a free re-read, and meta.notionalCredits is what the request counted (see limits & credits).

MCP tools return only the Markdown, as text. Scripts that want JSON use --json or the REST API.

Errors go to stderr as error: … plus a hint: … line with the next step.

Exit Codes Meaning
0 — Success, including empty results and pending transcriptions
1 internal_error Something broke on our side; retry, and quote the request id if it persists
2 invalid_input A bad flag or argument; the message names it
3 unauthenticated, forbidden Run scrollhound login, or check your account
4 not_found, unsupported_url The item doesn’t exist, or the link isn’t from a platform Scrollhound reads
5 rate_limited, spend_cap_reached, quota_exhausted, insufficient_credits Slow down, wait for your monthly limit or the daily quota to reset, or choose a plan (on a plan, buy extra credits) in your dashboard
6 upstream_unavailable The source is temporarily unavailable; retry in a few minutes
7 upgrade_required This CLI version is too old; run scrollhound update

Warnings (for example, less than 10% of your monthly limit left, or a newer CLI being available) go to stderr and never change the exit code.