The Subreddits AI Agent Builders Actually Use: 24 Communities, Measured

Nobody who publishes a list of the best subreddits for AI agent builders has measured one. Five pages currently rank for that query, four of them rank communities by feel, and the fifth states the right principle and then ranks against it.

TL;DR: Five curated lists rank the best subreddits for AI agent builders and not one publishes a number it collected. We measured 24 communities and 2,400 posts through the public Reddit data API on 2026-09-02. Subscriber count is an excellent predictor of raw attention and a poor predictor of agent-specific conversation: rank correlation with the mean score of the month's top posts is +0.857, and with the share of the newest 100 posts mentioning agent building it is -0.559, permutation p 0.0040 over 24 communities. r/mcp sits 18th of 24 on size and 1st on measured builder signal. r/ChatGPT is 1st on size and 16th on signal. The newest 100 posts span 13.6 hours in r/ClaudeCode and 431 days in r/AutoGenAI, so a fixed sample of 100 is not one measurement, it is 24 different ones.

That is not a complaint about effort. Several of those lists are written by people who clearly use these communities, and one of them states our central finding outright before ranking in a way that contradicts it. The gap is narrower and more specific: the question "which community should an agent builder be in" has an answer you can measure, and everyone answers it from memory instead.

So we measured it. On 2026-09-02 we read the about record for 24 communities, pulled the newest 100 posts from each, and pulled up to 100 top-of-month posts from each, through the public Reddit data API. That is 2,400 posts, 96 requests, and zero failed calls. Every number below is either measured in that pass, derived from it with the arithmetic shown, or cited to a named third party with a retrieval date, and each one says which it is.

Not affiliated with Reddit Inc. redditapis.com is an independent third-party REST proxy for Reddit's API. This guide is vendor-neutral: it publishes the raw columns so you can disagree with our weighting, names the limits of every measurement, and credits the competitor pages that got things right.

What are the best subreddits for AI agent builders in 2026?

Measured by us across 24 communities on 2026-09-02 through the public Reddit data API, the five highest on builder signal are r/mcp, r/AI_Agents, r/LLMDevs, r/n8n and r/LangChain. None of those five is in the top seven by subscriber count. The five lowest are r/redditdev, r/MachineLearning, r/RooCode, r/singularity and r/vibecoding, and two of those five are among the three largest communities in the basket. That inversion is the finding, and the rest of this guide is the evidence for it and the argument about what it does not prove.

The five, in composite order, with the size rank each one holds:

• r/mcp, 18th of 24 by subscribers, 1st on builder signal
• r/AI_Agents, 8th by subscribers, 2nd on signal, and the highest raw throughput in the basket
• r/LLMDevs, 3rd on signal
• r/n8n, 13th by subscribers, 4th on signal
• r/LangChain, 5th on signal

Here is the throughput number that most separates the two groups, the rate at which each community produces posts that are actually about building agents:

Before the full table, one caution about how to read it. The composite column is a weighting we chose, not a property of these communities. It puts 0.4 on the share of posts that mention agent building, 0.4 on the log of the rate at which those posts arrive, and 0.2 on comments per upvote, each min-max normalised across the 24. We picked those weights because they answer the question a builder is actually asking, which is whether the room is talking about the thing you are building and whether it answers you. Somebody optimising for reach should weight them differently and will get a different order. That is why every raw column sits beside the score.

The 24 communities, ranked on measured builder signal

#	Community	Subscribers	On-topic share	Agent posts per day	Comments per upvote	Signal score	Source
1	r/mcp	119,572	93.0%	34.73	1.17	89.5	derived
2	r/AI_Agents	433,287	70.0%	63.71	1.45	85.9	derived
3	r/LLMDevs	167,312	57.0%	17.94	1.724	76.4	derived
4	r/n8n	254,957	90.0%	7.59	0.865	75.7	derived
5	r/LangChain	106,454	82.0%	10.95	0.979	75.5	derived
6	r/AgentsOfAI	123,838	86.0%	10.96	0.596	72.4	derived
7	r/crewai	6,922	87.0%	1.41	1.021	66.9	derived
8	r/ClaudeCode	401,603	22.0%	38.86	0.87	53.6	derived
9	r/ClaudeAI	1,110,377	30.0%	45.87	0.439	52.7	derived
10	r/AutoGenAI	9,067	86.0%	0.2	0.418	47.8	derived
11	r/cursor	155,071	30.0%	5.06	0.771	44.6	derived
12	r/ChatGPTCoding	397,607	50.0%	3.46	0.179	44.1	derived
13	r/LocalLLaMA	815,926	18.0%	11.22	0.608	41.5	derived
14	r/artificial	1,332,093	28.0%	6.07	0.443	40.5	derived
15	r/ollama	135,960	25.0%	4.01	0.717	40.3	derived
16	r/ChatGPT	11,616,379	9.0%	12.74	0.442	35.9	derived
17	r/OpenWebUI	22,686	31.0%	0.99	0.696	35.0	derived
18	r/OpenAI	2,848,072	14.0%	5.13	0.447	33.2	derived
19	r/PromptEngineering	412,301	16.0%	2.91	0.488	31.5	derived
20	r/vibecoding	350,863	18.0%	4.89	0.167	31.2	derived
21	r/singularity	3,961,075	9.0%	1.81	0.293	23.1	derived
22	r/RooCode	18,684	22.0%	0.13	0.76	20.3	derived
23	r/MachineLearning	3,069,326	10.0%	0.59	0.482	19.7	derived
24	r/redditdev	86,637	6.0%	0.05	1.667	19.3	derived

n = 2,400 · as of 2026-09-02

The rank movement is easier to see on six communities than on 24, and the direction is consistent across the whole basket:

Across all 24, the average absolute rank movement between the two orderings is close to nine places. r/mcp and r/crewai each gain 17, r/LangChain gains 14, r/AutoGenAI gains 13. Going the other way, r/MachineLearning loses 20, r/singularity loses 19, r/ChatGPT loses 15 and r/OpenAI loses 14. Four communities barely move: r/RooCode holds 22nd on both, r/ollama moves one place, r/ChatGPTCoding moves one, r/ClaudeCode moves two. A ranking that shuffles everything would be suspicious. This one leaves the middle roughly alone and inverts the ends, which is what you would expect if size and topical density were measuring genuinely different things.

How did we measure this, and what exactly did we collect?

Three requests per community, run sequentially from one client on 2026-09-02, with the exact request shapes published so you can repeat them. The about record gives subscribers and the creation date. A listing call sorted by new at limit 100 gives everything behavioural: timestamps, authors, upvotes, comments and text. A top-of-month call gives the attention ceiling. Nothing here needs a field Reddit stopped returning, which matters more than it sounds and is the subject of a later section.

The three requests, per community:

• GET /api/reddit/sub/<name>/about for subscribers and the creation date
• GET /api/reddit/posts?sort=new&limit=100 for timestamps, authors, upvotes, comments and text
• GET /api/reddit/posts?sort=top&t=month&limit=100 for the attention ceiling

Exactly as issued:

# 1. size and age
curl -H "Authorization: Bearer $KEY" \
  "https://api.redditapis.com/api/reddit/sub/<name>/about"

# 2. behaviour: timestamps, authors, upvotes, comments, text
curl -H "Authorization: Bearer $KEY" \
  "https://api.redditapis.com/api/reddit/posts?subreddit=<name>&sort=new&limit=100"

# 3. the attention ceiling
curl -H "Authorization: Bearer $KEY" \
  "https://api.redditapis.com/api/reddit/posts?subreddit=<name>&sort=top&t=month&limit=100"

The basket was chosen deliberately rather than randomly, and that is a limitation worth naming first. We wanted four strata: dedicated agent communities (r/AI_Agents, r/mcp, r/LangChain, r/LLMDevs, r/AutoGenAI, r/crewai, r/AgentsOfAI, r/n8n), general AI communities (r/ClaudeAI, r/LocalLLaMA, r/OpenAI, r/singularity, r/artificial, r/MachineLearning, r/ChatGPT), agentic coding tools (r/cursor, r/ChatGPTCoding, r/vibecoding, r/ClaudeCode, r/PromptEngineering, r/RooCode, r/OpenWebUI) and runtime plumbing (r/ollama, r/redditdev). Sizes run from 6,922 subscribers in r/crewai to 11,616,379 in r/ChatGPT, three orders of magnitude, so no finding here can be blamed on comparing only small things to only small things.

ONE PASS, READ LIVE

What 24 communities cost to measure properly

2026-09-02

COMMUNITIES

24

POSTS ANALYSED

2,400

API CALLS

96

FAILED REQUESTS

0

Every subscriber count came back populated

Every created_utc came back populated

Post velocity spans 768x across the basket176.63 per day at the top, 0.23 at the bottom

The live active-user field returned null in 24 of 24Every one of those requests answered HTTP 200

Five communities could not fill a 100-item top-of-month pager/RooCode returned 1, r/AutoGenAI returned 2

Three requests per community on 2026-09-02, run sequentially from one client. The zero in the last column is what makes the null field a finding rather than a failure.

What the pass cost is worth stating plainly, because it is the reason nobody does this and the reason that excuse does not hold:

Ninety six requests. On a rate budget that comfortably accommodates it, the whole dataset behind this guide took a few minutes of wall clock. Anyone publishing a ranked list of eight or ten communities could collect the same evidence for a third of that. The reason curated lists carry no numbers is not that the numbers are expensive. If you want the mechanics of paging a listing further than one call reaches, the pagination rules cover the cursor behaviour, and the rate-limit picture covers what a sustained version of this costs.

The one methodological choice that deserves argument is the topic classifier. We match each post's title and body against a fixed list of 17 patterns: agent, agents, agentic, mcp, model context protocol, tool call, tool use, function call, langgraph, langchain, crewai, autogen, n8n, orchestrat, multi-agent, a2a and swarm. That list is blunt in both directions. It matches a post in r/singularity whose body happens to say "agentic video understanding" and misses a post in r/n8n titled "Built this order-processing workflow, would love feedback on the branching logic", which is agent work by any reasonable definition and contains none of our terms. We hand-checked samples in both directions and we ran the whole thing three ways, which is the subject of a later section. The short version is that the ordering barely moves.

Why is subscriber count the wrong number to rank on?

Because it predicts the wrong thing, and it predicts that wrong thing extremely well, which is what makes it so persuasive. Across the 24 communities, subscriber count correlates with the mean score of the month's top posts at Spearman rho +0.857. If your question is "how many people will see this", subscriber count answers it about as well as a single number can. Against the share of the newest 100 posts that mention agent building, the same number correlates at -0.559. Both of those are real, and they point in opposite directions.

What subscriber count does and does not predict, across the same 24 communities:

• Attention, mean score of the month's top posts: Spearman rho +0.857, p < 0.0001
• On-topic share, agent-building mentions in the newest 100: Spearman rho -0.559, p 0.0040
• Discussion depth, comments per upvote: Spearman rho -0.463, p 0.0252

How well subscriber count predicts each measured column

What subscribers is compared against	Spearman rho	Permutation p	Reading	Source
Mean score of the top posts this month	+0.857	under 0.0001	Strong. Size predicts attention very well.	derived
Posts per day	+0.654	0.0009	Real. Bigger communities are posted in more.	derived
Share of posts about building agents	-0.559	0.0040	Negative. Bigger communities are less on-topic.	derived
Comments per upvote	-0.463	0.0252	Negative. Bigger communities reply less per vote.	derived

n = 24 · as of 2026-09-02

Four correlations, one basket, and a sign flip between the first row and the third. Permutation p values come from 20,000 label shuffles rather than a normal approximation, because 24 is a small sample and a normal approximation on 24 points is a claim nobody should accept quietly. The p on the on-topic row is 0.0040 and on the comments-per-upvote row is 0.0252, so both clear a conventional threshold, and the attention row is under 0.0001.

The attention side of that trade is worth seeing directly, because it is genuinely large:

THE SAME COMMUNITIES, TWO DIFFERENT ANSWERS

Mean upvotes on the month's top posts, where the attention actually is

Point	Value (upvotes)
r/ChatGPT	1,980.8 upvotes
r/ClaudeAI	1,499.3 upvotes
r/singularity	1,247.3 upvotes
r/LocalLLaMA	1,022.5 upvotes
r/ClaudeCode	761.7 upvotes
r/AI_Agents	54.1 upvotes
r/mcp	15.2 upvotes
r/LangChain	11 upvotes

A top post in r/ChatGPT this month averaged 1,980.8 upvotes. A top post in r/mcp averaged 15.2. That is a factor of 130, and anyone telling you r/mcp is a better place to be seen is wrong. The claim is narrower: r/mcp's 100 newest posts carry 93 percent agent-building talk against r/ChatGPT's 9 percent, so the two communities answer different questions and only one of those questions is answered by a subscriber count.

There is a second reason the number misleads, and it has nothing to do with what it measures. Subscriber count is cumulative. It counts every account that ever joined and it never decays when someone stops reading, unsubscribes in spirit, or deletes the app. A community that was busy years ago and quiet since carries that old number forever. That is not a flaw Reddit should fix; it is simply what the field is. It becomes a problem only when a list treats it as a proxy for present activity, which every list we read does.

This is not a new observation. It circulates as folk wisdom inside the communities themselves, and off-platform too: a Hacker News comment from 2024 describes the mechanism directly, that a small community which grows past some threshold gets "overrun by the greater reddit population" and loses what made it worth being in. Inside the communities it is stated more bluntly:

r/

r/MachineLearning·u/fit-captain-6

[D] What are the best subreddits you follow for AI/ML/LLMs/NLP/Agentic AI etc?

00

Open on Reddit

The top answer in that thread, at 61 upvotes, is a person saying the community has not recovered from the 2023 API changes: "This sub used to be 10X better before the reddit mobile app API protests. Many active posters stopped posting and probably moved e.g. to twitter. This sub has never recovered after that. The content difference is night and day". The second-highest answer, at 33, argues against the premise of the whole genre: "On the whole Reddit is not the best place for this information though. It's too noisy". Neither of those people published a number either. Both of them are describing something our data can see.

Which communities are actually about building agents?

r/mcp, at 93 of the newest 100 posts matching agent-building terms, followed by r/n8n at 90, r/crewai at 87, r/AgentsOfAI and r/AutoGenAI at 86, and r/LangChain at 82. At the other end, r/redditdev sits at 6, r/singularity and r/ChatGPT at 9 each, and r/MachineLearning at 10. The gap between the two ends is a factor of 15 and it does not track size in the direction anyone expects.

• Densest: r/mcp 93 of 100, r/n8n 90, r/crewai 87, r/AgentsOfAI and r/AutoGenAI 86, r/LangChain 82
• Thinnest: r/redditdev 6, r/singularity and r/ChatGPT 9 each, r/MachineLearning 10

What that chart hides is volume, and volume is where the general communities claw back most of the difference. r/ChatGPT produces 141.57 posts per day at 9 percent on-topic, which is 12.74 agent-relevant posts per day. r/n8n produces 8.43 posts per day at 90 percent on-topic, which is 7.59. So the community that is 45 times larger and 10 times less relevant still puts more agent-adjacent material in front of you per day. Both numbers are true and a ranking that reports only one of them is misleading in a predictable direction.

Summed across the basket, the eight dedicated agent communities produce 147.5 agent-relevant posts per day, just over half the total. The seven general AI communities produce 83.4, and the seven agentic-coding communities produce 56.3. So the honest picture is a split rather than a hierarchy: half the agent conversation on Reddit happens in communities named after agents, and the other half happens in communities named after models and editors. A list that covers only the first half misses roughly 49 percent of the material, and a list that covers only the second half misses 51 percent.

For a concrete sense of what the highest-density community is actually discussing, this walkthrough of wiring custom agents through the Model Context Protocol covers the same ground r/mcp posts about daily:

If you want the equivalent on this site rather than on video, the guide to building a Reddit MCP server walks the server side and the agent-skill packaging guide covers the alternative shape, where the same capability ships as a skill rather than a server.

How much does posting volume differ between these communities?

By a factor of 768, which is larger than almost anyone assumes and large enough to break naive comparisons. r/ClaudeCode ran at 176.63 posts per day when we measured. r/AutoGenAI ran at 0.23. In between sits basically every rate you can imagine: r/ClaudeAI at 152.89, r/ChatGPT at 141.57, r/AI_Agents at 91.02, r/LocalLLaMA at 62.35, r/mcp at 37.34, r/LangChain at 13.35, r/redditdev at 0.89, r/RooCode at 0.58.

• Fastest: r/ClaudeCode at 176.63 posts per day
• Slowest: r/AutoGenAI at 0.23 posts per day
• Spread: a factor of 768 between them

What a page of 100 posts actually samples, per community

Community	Hours the 100 newest posts span	Posts per day	Distinct authors	Automation posts	Top-of-month posts returned	Source
r/ClaudeCode	13.6	176.63	100	0	100	measured
r/ClaudeAI	15.7	152.89	100	0	100	measured
r/ChatGPT	17.0	141.57	98	0	100	measured
r/AI_Agents	26.4	91.02	95	1	100	measured
r/LocalLLaMA	38.5	62.35	95	1	100	measured
r/mcp	64.3	37.34	69	0	100	measured
r/OpenAI	65.5	36.63	92	0	100	measured
r/LLMDevs	76.3	31.47	95	0	100	measured
r/vibecoding	88.4	27.15	85	0	100	measured
r/artificial	110.7	21.67	89	0	100	measured
r/singularity	119.4	20.11	66	0	100	measured
r/PromptEngineering	132.1	18.17	81	0	100	measured
r/cursor	142.2	16.88	91	0	100	measured
r/ollama	149.6	16.04	95	0	100	measured
r/LangChain	179.8	13.35	76	0	100	measured
r/AgentsOfAI	188.2	12.75	82	1	100	measured
r/n8n	284.6	8.43	82	0	100	measured
r/ChatGPTCoding	347.0	6.92	94	3	100	measured
r/MachineLearning	407.6	5.89	94	3	100	measured
r/OpenWebUI	752.3	3.19	85	1	94	measured
r/crewai	1,478.6	1.62	77	0	53	measured
r/redditdev	2,692.9	0.89	93	1	21	measured
r/RooCode	4,161.4	0.58	75	0	1	measured
r/AutoGenAI	10,350.8	0.23	60	0	2	measured

n = 2,400 · as of 2026-09-02

The column that does the real damage is the first one. The newest 100 posts covered 13.6 hours in r/ClaudeCode and 10,350.8 hours in r/AutoGenAI. That second figure is 431 days. So when a curated list puts r/AutoGenAI and r/ClaudeCode on the same page as peers, it is comparing a community whose visible front page turns over twice a day with one whose visible front page has been accumulating since the middle of 2025.

That difference has a practical consequence for anything you build on top. A single polling cadence cannot serve this basket: poll every hour and you will re-read the same page 24 times in r/AutoGenAI while missing seven posts in r/ClaudeCode. If you are building a monitor rather than a ranking, the webhook and polling comparison works through the cadence question properly, and the keyword-monitor build shows the shape in code.

What does a fixed sample of 100 posts really measure?

A different amount of time in every community, which is the single most under-stated problem in this genre. A listing call returns at most 100 items. It does not return the last 24 hours, or the last week, or any fixed period. It returns however far back 100 items happens to reach, and that depends entirely on how busy the community is.

• A listing call returns at most 100 items, never a fixed period
• Those 100 covered 13.6 hours in r/ClaudeCode
• The same 100 covered 10,350.8 hours, or 431 days, in r/AutoGenAI

This is why every table in this guide carries the window beside the figure. Comments per upvote over 13.6 hours in a fast community and over 431 days in a slow one are not the same measurement, and averaging them into a single leaderboard column without saying so would be dishonest. Our derived rate columns divide by the actual window rather than assuming a period, which fixes the arithmetic. It does not fix the deeper problem, which is that a fast community's 100 posts are all fresh and a slow community's 100 posts include material that has had a year to accumulate votes.

Two consequences follow, and the second one is easy to miss. First, a slow community's engagement figures are inflated relative to a fast one's, because old posts have finished collecting and new posts have not started. Second, a fast community's "posts with no engagement yet" count is inflated for exactly the mirror reason. Both of those biases run in the direction of making fast communities look worse. Our on-topic share is immune to this, because whether a post mentions agents does not change with age, which is one reason we weight it heavily.

If you want the general version of this argument applied to audience analysis rather than community ranking, the demographics measurement works through the same window problem across a different basket and reaches the same conclusion from the other side.

Does a bigger community give you more discussion, or just more upvotes?

More upvotes, and measurably less discussion per upvote. Comments per upvote across the newest 100 posts runs from 1.724 in r/LLMDevs and 1.667 in r/redditdev down to 0.167 in r/vibecoding and 0.293 in r/singularity. Subscriber count correlates with that ratio at Spearman rho -0.463, permutation p 0.0252.

• Deepest discussion: r/LLMDevs at 1.724 comments per upvote, r/redditdev at 1.667
• Shallowest: r/vibecoding at 0.167, r/singularity at 0.293

The ratio is worth explaining because it is easy to misread. It is the total comment count over the total upvote count for the page, not an average of per-post ratios, which would be distorted by the posts sitting at zero. A ratio above 1 means the community writes more replies than it casts votes, which is what a discussion forum looks like. A ratio of 0.17 means roughly six upvotes per comment, which is what a feed looks like: people scroll, they approve, they move on.

Read that against what people say they want from these communities. One commenter in r/AiBuilders put the distinction better than we can: "the best agent discussions tend to be in places where people share actual runs, failures, and fixes (not just 'I made an agent' posts)". Runs, failures and fixes generate comments. Finished projects generate upvotes. The ratio is a crude proxy for which of those a community is made of, and it separates the basket cleanly: seven of the eight dedicated agent communities sit above 0.59, and six of the seven general AI communities sit below 0.49.

There is one honest complication. r/redditdev scores 1.667 on this ratio and finishes 24th of 24 overall, because it produces 0.89 posts per day of which 6 percent are agent-related. High reply depth in a community that almost never posts about your topic is not useful to you. The ratio is a modifier, not a ranking, which is why it carries the smallest weight in the composite.

Is the live active-user count still returned by the Reddit API?

No, not with a value. We requested the about record for 24 communities on 2026-09-02. Every request returned HTTP 200. The active_user_count field came back null in 24 of 24.

The distinction that makes this a finding rather than an outage is that these were not failed calls. Each response carried a populated subscriber count, a populated creation date, a description, a language, a subreddit type and a URL. One field among them was empty. The field is still in the response shape; it just carries nothing. Our basket spans 6,922 subscribers to 11,616,379 and creation dates from 2006 to 2023, so the null is not a size artefact or an age artefact.

What that costs you is concrete. Subscribers and active users were the two halves of a size reading: one told you how many ever joined, the other told you how many were present. With the second gone, the about record answers only the accumulated question, and every engagement figure has to be derived from post listings instead. That is exactly what this guide does, and it is why the method section spends more time on a listing call than on the about record.

If you are building anything that assumed that field returns a number, the practical fix is to treat a null as missing rather than as zero, and to derive presence from post velocity. The subreddit-discovery guide covers what the about record does still return, and the analytics dashboard build covers the derived alternatives in more depth.

How much of this is written by bots?

Almost none of it, which surprised us and is worth reporting precisely because it contradicts the loudest complaint about these communities. Across 2,400 posts, accounts matching a bot naming pattern wrote 11. That is 0.46 percent. The highest single community was 3 of 100, in r/MachineLearning and in r/ChatGPTCoding. Seventeen of the 24 communities returned zero.

• 11 automation-named authors across 2,400 posts, which is 0.46 percent
• Highest single community: 3 of 100, in r/MachineLearning and r/ChatGPTCoding
• 17 of 24 communities: none at all

That result deserves three caveats stated up front, because a low number is easy to over-read. The check matches the name AutoModerator, any name ending in "bot", and any name carrying a bot separator such as a hyphen or underscore before "bot". A bot with a human-looking name is invisible to it, so 0.46 percent is a floor and not an estimate. The check covers submissions only; we did not classify comments, and comment spam is a different problem with a different rate. And a community's moderation may simply be removing automated submissions before a listing call sees them, which would produce this exact result for a reason that has nothing to do with how many bots try.

Even with those caveats, the direction is informative, and it is useful because a comparable measurement exists. On a different basket read on 2026-08-31, AutoModerator alone wrote 31 of the 100 newest posts in r/Python and 11 of 100 in r/datascience. So automation-heavy submission streams demonstrably exist on Reddit and they are visible to exactly this check. The AI and agent communities in our basket are not one of them. Whatever people mean when they say these communities are full of bots, the submission stream is not where it shows up.

For the rules side of that question, the bot rules guide covers what a community will and will not tolerate from an automated account, which matters if your agent is going to post rather than only read.

How concentrated is the posting in each community?

Less than you would guess, and the concentrated ones are not the ones you would pick. Distinct authors per 100 posts runs from 60 in r/AutoGenAI to 100 in r/ClaudeAI and r/ClaudeCode. Fifteen of the 24 communities returned 85 or more distinct authors per 100 posts, which means the typical community in this basket is a broad conversation rather than a handful of prolific posters.

• Most concentrated: r/AutoGenAI at 60 distinct authors per 100 posts
• Least concentrated: r/ClaudeAI and r/ClaudeCode, both at 100 of 100
• 15 of the 24 returned 85 or more

The two communities where every one of the newest 100 posts came from a different account, r/ClaudeAI and r/ClaudeCode, are also the two fastest in the basket at 152.89 and 176.63 posts per day. That is not a coincidence: at those rates a page of 100 covers under 16 hours, and it is unusual for one person to post twice in a working day. The slower communities show more concentration because their 100 posts span months and a regular contributor appears several times. So the concentration column is partly a window artefact, and it should be read as a floor on breadth rather than as a measurement of how many distinct people are in the room.

r/singularity at 66 distinct authors per 100 is the interesting exception, because it is not slow. It produces 20.11 posts per day, its page spans 119.4 hours, and a third of its posts still come from repeat accounts inside five days. That is a genuinely more concentrated submission stream than its neighbours at similar velocity, and it is consistent with the complaint people make about that community rather than with the one they make about bots.

What do the existing ranked lists get right, and where do they break?

The best of them gets the thesis right and the ranking wrong, which is a more interesting failure than being wrong twice. aibuilderclub's ranked list opens by stating: "subscriber counts are anti-signal: the biggest AI subs are news feeds, and the building happens in mid-sized ones." That is our finding, published two months before we measured it, and the page deserves credit for it.

• Gets right: the thesis that subscriber count is anti-signal
• Gets wrong: the ranking it then publishes against that thesis
• Never states: a condition under which its own ordering would be wrong

Then it ranks r/ClaudeAI and r/LocalLLaMA five stars out of five, ahead of r/AI_Agents at four. Measured on 2026-09-02, r/ClaudeAI carries 30 percent agent-building talk and r/LocalLLaMA carries 18 percent, against r/AI_Agents at 70 percent. r/ClaudeAI and r/LocalLLaMA are the two largest communities in that page's own top four. By its own stated principle, its top two picks are the news feeds it warns about.

What each page ranking for this query publishes, read on the live page

Page	Size numbers	Date shown	Posting frequency	Topic measurement	Source
redditmaster.com	None on the page	Updated for 2026, no day	No	No	published
aibuilderclub.com	None on the page	July 2, 2026	No	No, a five-star editorial rating	published
linkeddit.com	Rounded estimates	Updated June 19, 2026	No	No	published
permitly.dev	None on the page	None found	No	No	published
thehiveindex.com	Member counts, current	Last updated 4/7/2026	No	Claims a multi-factor rank	published

n = 5 · as of 2026-09-02

Read across that table rather than down it. What almost every one of these pages does not publish is not a size number, which two of them do carry. It is any figure describing how often people post or what the community is currently talking about. redditmaster's list carries no numeric figure of any kind in its body, and the Awesome AI Subreddits repo ranking eighth for this query is a categorised list of badge links with no size or activity data in its README. Five of five publish nothing on posting frequency. Five of five publish nothing on topical relevance. Five of five state nothing about what would make their ranking wrong.

One of the five deserves a genuine correction to our framing. thehiveindex is a directory rather than an article, it prints member counts, it prints a last-updated date of 4/7/2026, and its counts are current: it lists r/AI_Agents at 433K against our live 433,287, r/aiagents at 119K against 119,299, r/automation at 230K against 230,348, and r/AIBizOps at 534 members against a live 535. Four spot checks, four matches, one of them accurate to a single subscriber. A directory that maintains its numbers is a different thing from an article that does not, and lumping them together would be the same laziness we are complaining about.

TWO WAYS TO ANSWER THE SAME QUESTION

What a curated list can tell you and what a measured one can

	Curated list	This measurement
Names the communities	Yes	Yes
Explains what each is for	Yes, and often better	Only from the data
Publishes a collection date	Two of five did	Yes, 2026-09-02
Publishes a size figure	Two of five did	Yes, for all 24
Publishes how often people post	None did	Yes, for all 24
Measures topical relevance	None did	Yes, with the term list printed
States what would make it wrong	None did	Yes, per table
Survives being re-run by a reader	Not testable	96 calls, three per community

The comparison grid above is deliberately not a scoreboard we win. A curated list written by someone who has been in r/AI_Agents for a year knows things this measurement cannot see: which flairs get removed, which moderator dislikes launch posts, whether the culture shifted last month. Those are real and they are not in any listing call. The argument is not that measurement replaces judgement. It is that a page can carry both, and none of these carry the first.

The people inside these communities select between them far more carefully than any of the ranking pages do, and they select on purpose rather than on size:

r/

r/AI_Agents·u/LearnCons

How do you stay up to date with AI (especially Agents) without drowning? Looking for learning paths & routines

00

Open on Reddit

At 176 upvotes and 65 comments, that thread is builders answering the question this post measures. The highest-scoring reply, at 57 upvotes, argues the useful signal is not volume at all: "most agent failures aren't model failures. They're orchestration failures." A reply at 17 upvotes states the filtering problem outright, "Staying up to date does not equal staying productive," and then describes cutting sources deliberately rather than adding them. And one at 4 upvotes does the thing a ranked list cannot: it routes by role, telling the asker the answer depends on whether they are "an engineer, who is expected to build bespoke reliable agents," and pointing them at a narrow community on that basis.

That last one is the shape of the whole argument. A community is a fit for a job, not a prize for being large, and the person answering did not reach for a subscriber count to say so. Our on-topic share column is a crude machine version of the same judgement, and it is crude precisely where that reply is sharp: it can tell you a room is talking about agent building, and it cannot tell you the room is right for your role.

How stale is a circulating subreddit list?

Very, and the decay is systematic rather than random. A 56-entry list of "places you can promote your saas" circulated on X in February 2026 with 172 likes, each entry carrying a subscriber figure. We checked all 56 against a live about record request on 2026-09-02.

• 54 of 56 names resolved
• Median live count: 2.17 times the stated figure
• Only 5 of the 54 were within ten percent
• Worst single miss: r/ChatGPT, listed at 300K against a live 11,616,392, a factor of 38.7

Kalash

@kalashvasaniya

and here is the reddit list (someone shared in the comments, so i thought why not share it with you guys) list of places you can promote your saas v3 👀 r/Entrepreneur (2.1M) r/startups (1.3M) r/SideProject (200K) r/Indie_Hackers (45K) r/solopreneurs (180K) r/Bootstrapped (85K)

Fifty four of the 56 names resolved. The median live count was 2.17 times the stated figure. Only 5 of the 54 were within ten percent. The worst single miss was r/ChatGPT, listed at 300K against a live 11,616,392, a factor of 38.7. r/ClaudeAI was listed at 45K against 1,110,428, a factor of 24.7. r/OpenAI at 250K against 2,848,086, a factor of 11.4. r/singularity at 450K against 3,961,080, a factor of 8.8.

The direction is the tell. Forty three of the 54 resolvable entries were understated and only 6 were overstated, which is what you expect from a list that was accurate once and has been copied since. Reddit's AI communities grew fast through 2025 and 2026, so a figure frozen at any point in that period reads low forever. Nobody in the chain is being dishonest. The list says what it said when someone wrote it, and it has been reshared ever since with the date attached to the tweet rather than to the numbers.

A published article does better and still not well. We took the size column from a ranking page that states "April 25, 2026, updated June 19, 2026, subscriber estimates rounded", and checked all 24 of its entries the same way.

One ranking page, its published sizes checked against a live read

Community	Size the page states	Live subscribers	Live over stated	Source
r/n8n	30,000	254,959	x8.5	measured
r/ClaudeAI	150,000	1,110,428	x7.4	measured
r/perplexity_ai	60,000	203,382	x3.39	measured
r/SideProject	250,000	826,060	x3.3	measured
r/Automate	50,000	157,106	x3.14	measured
r/leadgeneration	25,000	66,874	x2.67	measured
r/cursor	70,000	155,071	x2.22	measured
r/SaaS	360,000	795,563	x2.21	measured
r/IndieDev	200,000	440,227	x2.2	measured
r/StableDiffusion	600,000	1,000,028	x1.67	measured
r/LocalLLaMA	500,000	815,941	x1.63	measured
r/LangChain	80,000	106,455	x1.33	measured
r/ChatGPT	9,000,000	11,616,395	x1.29	measured
r/agency	80,000	98,924	x1.24	measured
r/marketing	1,600,000	1,966,819	x1.23	measured
r/Entrepreneur	4,500,000	5,269,810	x1.17	measured
r/MachineLearning	3,000,000	3,069,333	x1.02	measured
r/B2BSaaS	30,000	28,631	x0.95	measured
r/OpenAI	3,000,000	2,848,089	x0.95	measured
r/digital_marketing	430,000	373,387	x0.87	measured
r/sales	1,100,000	601,107	x0.55	measured
r/AIEngineer	80,000	2,408	x0.03	measured
r/AgentLLM	40,000	did not resolve	n/a	measured
r/coldemail	20,000	did not resolve	n/a	measured

n = 24 · as of 2026-09-02

Twenty two of 24 resolved. The median ratio was 1.48, and 7 of the 22 were within 25 percent, which is a fair reading of "rounded". Nine were understated by a factor of 2 or more, which is not: r/n8n stated at 30K against a live 254,959, and r/ClaudeAI stated at 150K against 1,110,428. Rounding explains a row at 1.1x. It does not explain a row at 8.5x on a page updated ten weeks earlier.

Do the recommended community names even resolve?

Two of the ones we checked do not resolve to what the page meant, and one does not resolve to anything at all. This is a smaller problem than staleness in frequency and a larger one in consequence, because a reader following a wrong name lands somewhere real and empty rather than somewhere wrong and obvious.

• Two names resolve to something other than what the page meant
• One resolves to nothing at all
• An invented control name returns HTTP 400, which is what makes the HTTP 200 with a null body readable

Community names recommended by ranking pages, resolved live

Name as published	What the API returns	Live subscribers	Where it was published	Source
r/AIAgents	r/aiagents	119,299	permitly.dev FAQ, named as most focused	measured
r/AI_Agents	r/AI_Agents	433,287	The community most other lists mean	measured
r/AgentLLM	HTTP 200, every field null	none returned	linkeddit.com table, stated as 40K	measured
r/Indie_Hackers	r/indie_hackers	3	A 56-entry list shared on X, stated as 45K	measured
r/indiehackers	r/indiehackers	190,582	The community that list meant	measured
r/solopreneurs	r/solopreneurs	1,716	The same list, stated as 180K	measured
r/Solopreneur	r/Solopreneur	74,299	The community that list meant	measured

n = 7 · as of 2026-09-02

The r/AgentLLM case is the one worth walking through, because it shows why a status code needs a control before you interpret it. That name appears in a live ranking page's table with a stated size of 40K. Requesting its about record on 2026-09-02 returned HTTP 200 with every field null: no name, no subscriber count, no creation date. That looks like a not-found result, and reading it as one would be a guess. So we ran a control: a deliberately invented name, zzq_not_a_real_subreddit_9931, returned HTTP 400. An unrecognised name produces a 400. r/AgentLLM produces a 200 with an empty body, which is a different state and is what a name Reddit knows but exposes nothing about looks like. Private, banned and removed communities all present that way. What would falsify this is the same request later returning a count, and that is the check worth repeating before you act on it.

The near-miss names are simpler and more common. A guide's FAQ names r/AIAgents as one of the two most focused communities for agent builders. That name resolves to r/aiagents, which is real and carries 119,299 subscribers. The community almost everyone else means is r/AI_Agents, which carries 433,287. One underscore, 3.6 times the membership. The same list that carried the stale sizes above names r/Indie_Hackers, which resolves to a community with 3 subscribers, while r/indiehackers carries 190,582. And it names r/solopreneurs at 1,716 while r/Solopreneur carries 74,299.

None of that requires an API to catch. It requires clicking the link once. That nobody did is the same class of problem as not measuring: the list was assembled from memory and republished without a check.

Where should you read, and where should you post?

Those are two different rankings and no page we read separates them, which is the most actionable gap in the whole genre. Reading value tracks on-topic share and reply depth, which puts r/mcp, r/AI_Agents and r/LLMDevs at the top. Posting reach tracks the attention ceiling, which puts r/ChatGPT, r/ClaudeAI and r/singularity at the top, with top-of-month means of 1,980.8, 1,499.3 and 1,247.3 against r/mcp's 15.2.

• Read in: r/mcp, r/AI_Agents, r/LLMDevs
• Post in: r/ChatGPT, r/ClaudeAI, r/singularity
• No page we read separates the two rankings

The practical shape that falls out of the data is a two-tier habit rather than a single pick. Read the dense communities, because that is where a question about tool schemas or retry logic gets an answer from someone who hit it last week. Post where the reach is, when you have something finished and the community's rules permit it, and accept that the replies will be thinner. Nothing in this data supports picking one community and living in it.

That distribution logic gets stated plainly by people who do it for a living:

George Pu

@TheGeorgePu

Build it. Open source it. Post it on r/LocalLLaMA and Hacker News. That's the whole go-to-market now. I've watched repos go from zero to 50K stars off a single Reddit post. $0 spent on marketing. Quality is the floor. Traction comes first. Revenue finds you.

"Build it. Open source it. Post it on r/LocalLLaMA and Hacker News. That's the whole go-to-market now." Our numbers do not contradict that. r/LocalLLaMA carries 815,926 subscribers and a top-of-month mean of 1,022.5 upvotes, so it is genuinely one of the best places to be seen. It also carries 18 percent agent-building talk, so it is a poor place to learn how to build one. Those two facts sit together and only the first one appears in the promotion lists.

Before posting anywhere, read the rules through the API rather than from a screenshot, because they change and they are enforced. The subreddit-rules endpoint guide covers how to pull them programmatically, and the moderator and wiki guide covers the rest of a community's stated posture.

What does r/mcp look like up close?

It is the densest community in the basket and one of the smallest, which is the whole argument in one row. 119,572 subscribers puts it 18th of 24 on size. 93 of its newest 100 posts mention agent-building terms, which puts it first on topical density by 3 points. It produces 37.34 posts per day, so its front page turns over roughly every two and a half days, and it returns 1.17 comments per upvote, so people reply rather than scroll.

• 119,572 subscribers, 18th of 24 on size
• 93 of the newest 100 posts on topic, first on density by 3 points
• 37.34 posts per day, 1.17 comments per upvote

That 83 percent title-match figure is the one to hold onto. In most communities the title-only classifier finds far less than the title-and-body one, because agent talk shows up in the body of a post about something else. In r/mcp the topic is in the headline: 83 of 100 titles say it outright, another 10 say it in the body, and 7 posts are about something else entirely. Three of those seven, read by hand, were a personal knowledge-management question, a UK property data listing and a trip-planning tool, which is what a small community's off-topic tail looks like.

The attention ceiling is the trade. A top-of-month post in r/mcp averaged 15.2 upvotes across 100 posts. If your goal is a launch, that number should stop you. If your goal is to find someone who has debugged an authentication gateway in front of a Model Context Protocol server this week, r/mcp is the highest-yield room in the basket and it is not close.

The same shape appears in the two other narrow communities. r/LangChain carries 82 percent on-topic at 106,454 subscribers and an 11.0 top-of-month mean. r/crewai carries 87 percent at 6,922 subscribers and a 1.5 mean, and it could only fill 53 of a requested 100 top-of-month posts, which is itself a size signal the subscriber count does not give you.

What does r/AI_Agents look like up close?

It is the only community in the basket that is both large and dense, and that combination is why it takes second place on our weighting and first place on raw throughput. 433,287 subscribers puts it 8th of 24. 70 percent on-topic puts it 7th. 91.02 posts per day puts it 4th. Multiply the last two and it produces 63.71 agent-relevant posts per day, the highest figure in the basket by a margin of 39 percent over r/ClaudeAI.

• 433,287 subscribers, 8th of 24
• 70 percent on topic, 7th; 91.02 posts per day, 4th
• 63.71 agent-relevant posts per day, the highest in the basket

Its reply depth is 1.45 comments per upvote, third highest, and its top-of-month mean is 54.1 upvotes, which is 3.6 times r/mcp's and 2.7 percent of r/ChatGPT's. So it sits in the middle of the attention distribution and near the top of everything else. If someone insisted on one community, this is the defensible answer, and it is the answer that the SERP itself gives: Google ranks r/AI_Agents first for the query this article targets, ahead of every article about it.

The thread that best shows what the community is for is not a project announcement. It is a 2,481-upvote, 464-comment argument about why agent projects fail:

r/

r/AI_Agents·u/Decent-Phrase-4161

I build AI agents for a living. It's a mess out there.

00

Open on Reddit

Read the replies rather than the post. One at 27 upvotes: "The most successful AI integrations I've created were embedded in workflows where the AI only actually operated on very small individual parts, where a decision was needed to make a fuzzy-logic style conclusion, and the decision-tree was very small." Another at 14 asks whether the post itself was written by a model. That is a community auditing its own material in public, and it is precisely the behaviour the comments-per-upvote ratio is a proxy for.

If you want the practical version of what people in that thread are describing, the complete guide to tool use and agentic workflows covers the patterns, and the agent data-layer guide covers what sits underneath a Reddit tool call when your agent makes one.

How sensitive is this ranking to how we defined agent talk?

Barely, and we tested it three ways rather than asserting it. The classifier is the weakest link in this whole measurement, so the honest thing is to vary it and publish what happens. We ran the same 100 posts per community against three different definitions: the term list matched against titles only, the same list matched against titles and bodies, and a wider list adding workflow, automation, automate, pipeline, rag and vector store, matched against titles only.

• Definition 1: the term list against titles only
• Definition 2: the same list against titles and bodies
• Definition 3: a wider list against titles only

The absolute numbers move a lot. r/ClaudeAI reads 6 percent on titles alone and 30 percent on titles and bodies, a factor of five. The ordering does not. Spearman rank correlation between the title-only ranking and the title-and-body ranking is 0.918 across all 24 communities, and between title-only and the wider list it is 0.981. The headline correlation survives too: subscriber count against on-topic share is -0.559 under the title-and-body definition and -0.542 under title-only.

There is a fourth check worth more than the other three, because it tests stability rather than definition. The second pass ran roughly thirty minutes after the first and re-pulled the newest 100 posts from every community. Twenty three of the 24 returned an identical on-topic share and the twenty fourth, r/vibecoding, moved by one percentage point. Spearman between the two passes is 1.0. That is a weaker check than it looks for the fast communities, where thirty minutes rolls over three or four posts out of 100, and a genuinely strong one for the slow ones, where nothing changed because nothing could have. It rules out the most boring failure mode, which is that we misread a transient page.

What none of this rules out is that our term list is the wrong list. Somebody measuring "communities where agent builders get useful answers" rather than "communities where agent words appear" would build a different classifier and might get a different answer. We publish the regex so that argument can be had with data on both sides.

What would make this ranking wrong?

Six things, and each of them is a real way this ranking could be misleading rather than a disclaimer for form's sake. We list them because not one of the five pages ranking for this query states a single condition under which its own ordering would be wrong, and a ranking that cannot be falsified is an opinion with numbers attached.

• The basket is ours, and a different 24 would produce different correlations
• The classifier is a term list, not an understanding of the post
• The window differs per community by design, and that is a confound as well as a finding

The basket is ours. Twenty four communities chosen to span four strata is not a random sample of Reddit, and a different 24 would produce different correlations. The specific vulnerability is that we included eight dedicated agent communities by design, and those are small and dense by definition, so some of the negative correlation between size and topic is baked into the selection. The defence is that the correlation also holds within the general-AI stratum alone, where r/artificial at 1,332,093 subscribers carries 28 percent and r/ChatGPT at 11,616,379 carries 9. A basket drawn to avoid that objection entirely that returned a positive rho would falsify this.

The window is one day. Every figure here is 2026-09-02. Communities move: a launch week inflates velocity, a moderation change shifts topical density, and a subscriber count only goes up. The half-life on this data is months rather than years, and the figure most likely to be wrong first is post velocity.

The classifier is a regex. Covered above. It matches "agentic video understanding" in r/singularity and misses "order-processing workflow" in r/n8n. The ordering survived three definitions, which is evidence, not proof.

The weighting is a choice. The composite score puts 0.4 on topical share, 0.4 on rate and 0.2 on reply depth. Nothing in the data selects those weights. Change them and the order changes, which is exactly why the raw columns are printed beside the score and why the tables are the deliverable rather than the leaderboard.

The top-of-month sample is uneven. Five communities could not return 100 top posts for the month: r/RooCode returned 1, r/AutoGenAI 2, r/redditdev 21, r/crewai 53, r/OpenWebUI 94. A mean over 1 post and a mean over 100 posts are not comparable, and the attention column for those five is weaker than for the other 19. We report it rather than dropping it, because the fact that a community cannot fill a top-of-month page is itself information about the community.

The measurement is of submissions. Comments are where a lot of the value in these communities lives, and we classified none of them. A community whose posts are launch announcements and whose comments are teardowns would score worse here than it deserves, and the reply-depth ratio is only a crude signal for that.

FROM ONE LISTING CALL TO FIVE COLUMNS

Which request each measured column is actually built from

timestampstextcountsrate

01About recordOne call per community

02Newest 100 postsOne listing call per community

03Top of the monthOne call, does not always fill

04Subscriber countThe only stable size figure

05Observation windowOldest to newest created_utc

06On-topic shareTitles and bodies against a term list

07Reply depthComments over upvotes

08Attention ceilingMean score of the month's top

Every one of those limits is a consequence of the same design decision, which is that the whole pass had to be cheap enough that a reader could repeat it. Three requests per community keeps it under a hundred calls. Adding comment classification would multiply that by roughly the mean comment count, and the guide would then be describing something nobody will re-run.

How do you run these measurements yourself?

Three requests per community and six derived columns, which is a loop over a list of names and roughly forty lines of code. The point of publishing it is that a reader should be able to re-run this basket, or a different one, and get numbers they can compare against ours rather than having to take ours on trust.

Start with the about record, which is one call and gives you the subscriber count and the creation date:

curl -s -H "Authorization: Bearer $KEY" \
  "https://api.redditapis.com/api/reddit/sub/mcp/about"

Then the listing, which is where everything behavioural comes from:

curl -s -H "Authorization: Bearer $KEY" \
  "https://api.redditapis.com/api/reddit/posts?subreddit=mcp&sort=new&limit=100"

Every item in that response carries created_utc, author, upvotes, comments, title and text. From those six fields you can compute every column in this guide:

import statistics

def measure(posts, term_re):
    ts = [p["created_utc"] for p in posts]
    window_h = (max(ts) - min(ts)) / 3600.0
    ups = [p["upvotes"] or 0 for p in posts]
    cms = [p["comments"] or 0 for p in posts]
    on_topic = [
        p for p in posts
        if term_re.search((p["title"] or "") + " " + (p["text"] or ""))
    ]
    return {
        "window_hours": round(window_h, 1),
        "posts_per_day": round(len(posts) / (window_h / 24.0), 2),
        "distinct_authors": len({p["author"] for p in posts}),
        "median_upvotes": statistics.median(ups),
        "comments_per_upvote": round(sum(cms) / sum(ups), 3),
        "on_topic_pct": round(100.0 * len(on_topic) / len(posts), 1),
    }

Four rules make the result worth trusting, and skipping any of them puts you back where the curated lists are.

State the window beside every figure. Two communities compared over different observation windows are not compared at all, and a fixed post count guarantees different windows. This is the one that gets skipped most often and it is the one that invalidates the most.

Publish your term list. Whatever you count as on-topic is a judgement, and the only way it becomes evidence is if a reader can disagree with it specifically rather than in general.

Run a control that must fire. Ours was the invented subreddit name that returned HTTP 400, which is what told us that r/AgentLLM's HTTP 200 with a null body meant something different. Without that control we would have written "does not exist" and been guessing.

Say what would make you wrong. If you cannot name the result that would falsify your ranking, you have published an opinion with numbers attached to it, which is worse than an opinion.

For the endpoint reference behind all of this, the search API tutorial covers query-shaped discovery, the comments endpoint guide covers the half of this we did not measure, and the community-discovery guide covers finding names to put in the loop in the first place. If you want to run this on a schedule rather than once, the monitoring webhook guide covers delivery and the trending-topic detector covers the change-detection layer on top.

Collecting public Reddit data programmatically is governed by Reddit's Data API Terms, and the positions we take on that are covered in the guide to what is and is not permitted. Everything in this guide is a read of publicly visible listings.

What should this change about how you pick a community?

Three things, and only the third is really about Reddit at all. The first is that the question is not singular, the second is that every published figure has a shelf life nobody prints, and the third is that a belief everyone holds is usually one afternoon of measurement away from being a finding.

• Pick against a question, not against a list
• Treat every published figure as having a shelf life nobody prints
• Measure the belief before repeating it

Pick against a question, not against a list. "Best subreddits for AI agent builders" is not one question. It is at least three: where do I learn, where do I get answered, and where do I get seen. Our data answers all three differently and the correct picks barely overlap. r/mcp is first on the first two and last but one on the third. r/ChatGPT is the reverse. Any single ranking has silently chosen one of those questions for you, and none of the pages we read says which.

Treat every published number as dated. The median entry in a seven-month-old circulating list understated a community by a factor of 2.17. The median entry in a ten-week-old article understated by 1.48. One directory was accurate to a single subscriber. The variable is not the format, it is whether anybody re-reads the source. If a number in a list has no date attached, the honest assumption is that it is old.

Measure the thing you are about to rely on. This is the part that generalises past subreddits. The whole reason this guide exists is that a question everyone answers from memory turned out to have a checkable answer costing 96 requests and an afternoon. The gap between "everyone knows the big AI subs are noise" and "subscriber count correlates with on-topic share at -0.559 with a permutation p of 0.0040 across 24 communities" is the difference between a belief and a finding, and it is not an expensive gap to close.

Verdict

Subscriber count is a real signal that answers a real question, and it is the wrong question for an agent builder. Across 24 communities measured on 2026-09-02 it predicted the mean score of the month's top posts at rho +0.857 and the share of current conversation about building agents at rho -0.559. Both numbers are true. Only one of them appears on any of the five pages currently ranking for this query.

• Attention: rho +0.857, which subscriber count predicts well
• On-topic conversation: rho -0.559, which it predicts backwards
• Only the first is published anywhere else

If you want a single answer: r/AI_Agents, because it is the only community in the basket that is both large and dense, producing 63.71 agent-relevant posts per day, the highest figure we measured. If you want the best room rather than the biggest, r/mcp, at 93 percent on-topic and 1.17 comments per upvote from 119,572 subscribers. If you want reach, r/ChatGPT and r/ClaudeAI, whose top posts this month averaged 1,980.8 and 1,499.3 upvotes, and accept that 9 and 30 percent of what you read there will be about the thing you are building.

What we would not do is take any of those three as settled. The half-life on this data is months. The classifier is a regex we wrote. The weighting is ours. What is durable is the method: three requests, six columns, a stated window, a published term list, a control that must fire, and a sentence saying what would make it wrong. That costs 96 API calls for 24 communities, and it is the only part of this guide still worth anything in a year.

The alternative is what the SERP currently offers, which is five pages telling you where to be, assembled from memory, two of them printing sizes that are wrong by up to a factor of 8.5, one of them recommending a community that does not resolve, and none of them naming the date they were checked. Those pages are not badly intentioned. They just never opened the API, and it is right there.