Pushshift Alternative: What Replaced It, and What ThreadSnoop Adds

Pushshift was the default way to search Reddit's full history — free, comprehensive, and relied on by researchers, moderators, and developers for years. Reddit's 2023 API changes cut off the firehose access Pushshift depended on, and self-serve public access never really came back — what's left is a restricted academic/moderator program, not something you can sign up for and start querying. A handful of community projects picked up the slack. Here's the honest landscape, and where ThreadSnoop fits.

What actually happened to Pushshift

Pushshift ingested Reddit's full post/comment stream in real time and made it searchable going back years — for a long stretch, it was the closest thing Reddit had to its own historical search. When Reddit locked down API access in 2023 (the same change that pushed pricing toward the enterprise tier and eventually contributed to GummySearch shutting down), Pushshift lost the firehose feed it depended on. Public, self-serve access to Pushshift's own API effectively ended — what remains is a much narrower program for approved researchers and moderators, not something a developer can sign up for today.

What replaced it: PullPush and Arctic Shift

Two community projects picked up the gap. PullPush deliberately mirrors Pushshift's original interface — if you had an old Pushshift script, pointing it at PullPush's base URL is often close to a drop-in swap. It's free, and it's also run on donated infrastructure with the rate limits and occasional outages that come with that: it reports roughly 15 requests/minute as a soft limit, 30/minute hard, and 1,000/hour overall, with outages documented on and off since it launched. Arctic Shiftis the other major successor — a dump-based archive, rebuilt independently rather than mirroring Pushshift's API shape.

Worth disclosing directly: Arctic Shift is what ThreadSnoop's API is built on. We don't operate our own Reddit archive — we read from the same successor lineage PullPush belongs to, and the value we add sits on top of it, not instead of it.

What ThreadSnoop adds on top of a free mirror

Nothing here is that PullPush or Arctic Shift are unreliable in some disqualifying way — they're real, actively used projects run by volunteers, and treating Reddit's historical archive as a labor of love rather than a funded product is exactly why they can stay free. The trade you're making by calling one directly is that you absorb whatever that means day to day: a tighter, shared rate limit, a service that can go down without warning, and no metering or usage visibility of your own if something upstream changes.

ThreadSnoop sits on the same underlying data with that operational work already done: a per-key rate limit instead of a rate limit shared across everyone hitting a free mirror, automatic failover between direct and proxied routing so a single upstream hiccup doesn't become your outage, normalized responses in Reddit's own field names, and an MCP server so any MCP-compatible agent — Claude, Codex, Cursor, and others — can call it directly instead of you writing integration code against a mirror's API shape. The API is also documented with a plain OpenAPI spec, so any AI agent that can read one and make an HTTP call works too, MCP or not. The historical query pattern itself — after=/before= as epoch time or a relative window like 7d — is the same idea Pushshift made popular, now behind a key instead of an open endpoint.

Bottom line

Pushshift's self-serve days are over, but the historical-search capability it made popular didn't disappear — it moved to a small set of community successors, and ThreadSnoop is a maintained, metered API built on that same lineage rather than a separate data source. If you want that query pattern without absorbing a free mirror's rate limits and uptime, 1,000 free Reddit reads are enough to see the difference: get a free API key.

Frequently asked questions