THREADPRINT

what works, and what doesn't

The honest list

THREADPRINT can only print a thread if the platform will hand over a post, its engagement, and its replies from a public link. Plenty won't. Every entry below was tested directly rather than taken from documentation, and it's re-checked automatically each week in case something opens up.

Live

3

Working right now. Paste a link and it prints.

PlatformAlso coversWhat we can getData costNotes
FarcasterEvery Farcaster client — Farcaster app, Supercast, Recaster, Herocast, Base App, FireflyFull post, likes, recasts, reply count, quote count, view count, tips, nested replies with their own engagement, list of likers$0.00Free public client API, no key. Richer than the paid Neynar API, which moved to x402 pay-per-call at $0.01/request in 2026 — the entire revenue of a 1c product. All Farcaster clients read the same casts, so one adapter covers the whole ecosystem.
BlueskyBluesky and any AT Protocol appview (deer.social, Blacksky, Ouranos)Full post, likes, reposts, replies, quote count, already-nested reply tree with per-reply engagement$0.00The public AppView needs no key and returns the richest data of any platform we support — it is the only one that gives a true quote count for free.
Mastodon & the FediverseMastodon, Akkoma, Pleroma, GoToSocial, Glitch-soc, Hometown — thousands of independent serversFull post, favourites, boosts, reply count, full descendant tree with per-reply engagement$0.00All four server families tested answer the identical /api/v1 endpoints, so one adapter covers the whole network. No quote count exists anywhere in the Mastodon API. Some servers restrict public API reads and will need login.

Verified, not shipped

8

Tested and confirmed working. An adapter hasn't been written yet.

PlatformAlso coversWhat we can getData costNotes
Hacker Newsnews.ycombinator.comStory, score, full nested comment tree$0.00Free Firebase API, no key, no rate limit in practice. Per-comment scores are not public, only the story score.
Lemmylemmy.world and every Lemmy instancePost, upvotes/downvotes, full comment tree with per-comment scores$0.00Open API, no key. The closest thing to a working Reddit substitute.
Stack ExchangeStack Overflow and all Stack Exchange sitesQuestion, score, answers with their own scores, comments$0.00Free API, 300 requests/day without a key and 10,000 with one. Threading is question/answer/comment rather than a reply tree.
NostrAll Nostr relaysNote, reactions, reposts, replies — assembled by querying relays$0.00Free and open, but engagement must be counted by querying reaction events across relays rather than reading a count, so results vary by which relays you ask.
Lens ProtocolLens and its clients (Hey, Orb)Publication, reactions, mirrors, comments$0.00Public GraphQL API responds without a key.
WikipediaAll Wikimedia projectsArticle, revision history, talk-page discussion threads$0.00Completely open. The content model is articles and talk pages rather than posts and replies, so it needs its own renderer.
Misskey & Sharkeymisskey.io, Sharkey, FirefishNote, reactions, renotes, replies$0.00Federates with Mastodon but does NOT answer the Mastodon API — tested and it 404s. Needs a separate adapter against its own /api endpoints.
YouTubeyoutube.comVideo, view/like counts, full comment threads with per-comment likes$0.00 within the free quotaFree API key with a 10,000-unit daily quota — roughly 5,000 extractions a day at 2 units each. Comments are a thread list rather than a deep tree. Genuinely viable, just not a 'social post'.

1

The data exists, but it costs more to fetch than THREADPRINT charges.

PlatformAlso coversWhat we can getData costNotes
X (Twitter)x.com / twitter.comPost, likes, reposts, replies, quotes, views — all available~$0.005 per post — a 50-reply thread costs ~$0.26The data is there, the price isn't. X discontinued its free tier in February 2026 and moved to pay-per-use at $0.005 per post read. A single thread can cost 25x what we charge, so X cannot ride the 1c price and would be quoted separately before payment.

Blocked by terms

1

The API works, but the terms of service rule out a paid product.

PlatformAlso coversWhat we can getData costNotes
Redditreddit.comPost, score, full comment tree — technically excellent~$12,000/mo minimum commercial contractBlocked on terms, not capability. The unauthenticated JSON endpoints now return 403, the free API tier explicitly prohibits commercial use, and the smallest commercial agreement starts around $12,000/month. Lemmy is the workable substitute.

No public access

5

No public way to read another user's post and its replies. No workaround found.

PlatformAlso coversWhat we can getData costNotes
Threadsthreads.netYour own posts onlyn/aThe Threads API only reaches content owned by the authenticated account. There is no endpoint for an arbitrary public post's replies. Threads is federating with the Fediverse, so some posts may become reachable through the Mastodon adapter over time — worth re-checking.
Instagraminstagram.comYour own business account onlyn/aThe Graph API reaches only accounts you own or manage. oEmbed returns a title and thumbnail with no engagement data and no comments. No workaround exists.
Facebookfacebook.comPages you own onlyn/aSame restriction as Instagram — both run on the Graph API. Arbitrary public posts are not readable.
TikToktiktok.comYour own videos onlyn/aThe Display API covers your own content. The Research API exists but is limited to approved academic institutions. oEmbed gives a title and no engagement.
LinkedInlinkedin.comNone for third-party postsn/aAccess is restricted to approved partners. No public read path to another user's post or its comments.

Why one adapter covers so much

Farcaster, Bluesky and Mastodon are protocols, not websites. Every Farcaster client — Supercast, Recaster, Herocast, Base App — reads the same casts, so supporting a new one is a line of URL parsing. Every AT Protocol service answers the same API as Bluesky. Mastodon, Akkoma, Pleroma, GoToSocial and Glitch-soc all answer identical endpoints, which is why one integration reaches thousands of independent servers. That's three adapters covering most of the open social web.

The closed platforms are a different story, and no amount of engineering gets around it: Instagram, Facebook, TikTok, Threads and LinkedIn simply have no public endpoint for another person's post and its replies.