Reddit's API costs $12,000—but the RSS door is still open
The coffee shops in Brooklyn Heights are full this morning, every table claimed by someone nursing a latte and squinting at a screen. Outside, the August sun has already turned the pavement sticky, and the air conditioning hums louder than the conversation.
Reddit’s API costs $12,000 a year but RSS endpoints are still free
Reddit killed affordable API access in 2023, but the old RSS feeds still work—unmetered, unpriced, and unannounced.
Reddit’s API pricing landed at $12,000 per year for 50 million requests. For most operators monitoring subreddits for content ideas, brand mentions, or niche-topic research, that’s untenable. The pricing killed Apollo, RIF, and a generation of third-party tools. But Reddit’s RSS endpoints—the ones appending .rss to any subreddit, user, or search URL—remain live, free, and unmetered.
The RSS feeds deliver the same post titles, timestamps, authors, and permalinks you’d pull via API. They don’t require authentication, rate-limit headers, or OAuth flows. You parse XML instead of JSON, and you lose comment threading and vote counts, but for monitoring, alerting, or feeding a content-research pipeline, RSS does the job. The catch: Reddit has never formally committed to keeping RSS available. There’s no SLA, no documentation update since 2018, and no public statement on longevity. Operators relying on these feeds are one product decision away from needing a new workflow.
If you’re running a newsletter that curates from niche subreddits, building a monitoring dashboard for client mentions, or feeding subreddit activity into a social-listening tool, RSS is the only free path left. The alternative is paying $12,000 or scraping HTML—which violates terms of service and breaks every time Reddit redesigns a page.
TACTIC
WordPress REST API rate limits break sync tools before you notice
Most managed WordPress hosts throttle REST API requests to 60 or 100 per minute, but they don’t surface the limit until you hit it. If you’re running automated workflows—syncing subscriber counts to a dashboard, pulling post metadata into Airtable, or triggering Zapier actions on publish—you’ll see intermittent failures with no clear error. The problem compounds when you connect multiple tools to the same endpoint. Knowing your host’s ceiling and how to identify which tool is consuming your quota prevents silent breakage mid-campaign.
READER QUESTION
When saving AI prompts costs more time than rewriting them
Storing prompt templates in Notion, Text Expander, or a dedicated library sounds efficient until context drift makes every saved prompt feel wrong. A prompt that worked in March assumes a product name, audience definition, or tone you’ve since changed. Operators spend more time editing old templates than writing fresh prompts that reflect current reality. Version control helps, but only if you’re disciplined about tagging context and dating iterations. Most of the time, starting from a blank slate is faster than debugging why last month’s prompt no longer delivers useful output.
WORTH READING
Newsletter A/B tests need 24–48 hours to resolve—not one
Most email platforms can’t call an A/B test winner in real time. Beehiiv, ConvertKit, and Mailchimp wait for opens, clicks, and delayed engagement to stabilise before declaring a result. Refreshing the dashboard an hour after send and picking the variant with the higher open rate costs you statistical validity. Platforms that auto-select a winner typically wait 24 to 48 hours, and manual tests should follow the same patience. Ending early biases toward subject lines that trigger immediate curiosity over those that drive sustained engagement or conversions later in the window.
Know someone who would like this? Forward today’s email—every operator we reach is one closer to running an online business with a little less friction.