# Dev.to for devtool founders: how to find developers asking for tools (2026)

> Find developers asking for tools on Dev.to: real #discuss and #help counts from the Forem API (Nov 21, 2026), copy-paste API calls, and DEV's promo rules.

Canonical: https://useneedle.net/blog/find-developers-asking-for-tools-devto
Published: 2026-11-21

Most of Dev.to is people writing, not people asking. In the seven days to November 21, 2026, the #webdev tag alone got roughly 630 posts a day, while #help got 13 posts all week. If you're a devtool founder looking for developers who want a tool like yours, the volume is a trap: the asks sit in a small slice of #discuss and, more often, in the comments under write-ups.

I pulled a week of posts from DEV's public API, read the comment threads on the busiest ones, and checked the community rules. Here's what's there, where to look, and how to reply without your account getting flagged.

**Disclosure:** I build [Needle](https://useneedle.net), which finds public posts where people ask for a tool and drafts a reply for a human to review. Dev.to is one of the networks it covers. Weigh my take accordingly.

---

## In brief

- **Volume isn't signal.** 617 #discuss posts and 1,006 #showdev posts went up in the week to Nov 21, 2026. 69% of the #discuss posts and 88% of the #showdev posts had zero comments.
- **Real asks exist but are few.** Of 617 #discuss titles, 138 contained a question mark and only a handful were genuine "what do you use for X" questions.
- **Comments are where tool talk happens.** In a 42-comment thread comparing web scraping APIs, about a fifth of the comments compared tools, pricing or failure modes.
- **The API is open for reading.** `/api/articles/latest?tag=discuss` and `/api/comments?a_id=ID` need no key. The search endpoint matched loosely in my tests, so filter titles yourself.
- **Promotion has a home and limits.** Use #showdev for launches, keep it "not overly corporate or salesy," disclose AI help, and don't use AI to write comments.

---

## What is Dev.to (and Forem)?

Dev.to, also called DEV Community, is a blogging and discussion site for software developers. It runs on [Forem](https://github.com/forem/forem), which its README describes as "open source software for building communities" and "the platform that powers dev.to." Posts of every kind (tutorials, discussion questions, help threads, launches) are called "articles" in the API, and each one carries a few tags.

The tags are the closest thing DEV has to subreddits. Each tag page shows its own submission guidelines. These are the ones that matter for finding tool requests, quoted from the tag pages on November 21, 2026:

| Tag | Its guidelines say | Useful for |
|---|---|---|
| [#discuss](https://dev.to/t/discuss) | Posts "should include a question, prompt, or topic that initiates a discussion in the comments section." | "How do you handle X" and "what do you use" threads |
| [#help](https://dev.to/t/help) | "To be used when you need to ask for help, not to share an article you think is helpful." Opinion questions about a technology belong in #discuss. | Specific problems; low volume |
| [#showdev](https://dev.to/t/showdev) | "For showing off projects and launching products. Please make posts community-driven and not overly corporate or salesy." | Your launch post; also competitor launches |
| #webdev, #devops, #ai, etc. | Topic tags | Huge volume, mostly tutorials |

---

## How much does Dev.to actually ask for tools? A week of numbers

I used `/api/articles/latest?tag=<tag>&per_page=1000` and counted posts published from November 14 to November 21, 2026 (UTC). I cross-checked #discuss and #help with `/api/articles?tag=<tag>&top=7`, which returned 603 and 13.

| Tag | Posts in 7 days | Zero comments | Posts with 5+ comments | Most comments on one post |
|---|---|---|---|---|
| #discuss | 617 | 69% | 68 | 178 |
| #showdev | 1,006 | 88% | 13 | 45 |
| #help | 13 | 77% | 0 | 3 |
| #webdev | ~3,000 in 4.8 days (~630/day) | 93% | 5 | 20 |

Median comments per post was zero for every tag. Median reactions too.

The busiest #discuss threads of the week were community prompts ("What does DEV stand for?", 178 comments; "Say Hello in Your Language!", 58), AI-agent essays and DEV's own roundups. Those are good for being visible in the community. They're not where buyers are.

The genuine tool questions looked like this (titles as posted, comment counts on Nov 21):

- [How do you keep scrapers from breaking every time a site changes?](https://dev.to/zhtech/how-do-you-keep-scrapers-from-breaking-every-time-a-site-changes-4p5h) (#discuss, 2 comments)
- [Running more than one coding agent at once: how do you watch them all?](https://dev.to/gautamtalksdev/running-more-than-one-coding-agent-at-once-how-do-you-watch-them-all-dpk) (#discuss, 4 comments)
- [How do you scope GitHub tokens for coding agents?](https://dev.to/gautamtalksdev/how-do-you-scope-github-tokens-for-coding-agents-3jm0) (#discuss, 3 comments)
- [Developers, what do you use to monitor your websites and APIs?](https://dev.to/nev_eaf9cd092d66e/developers-what-do-you-use-to-monitor-your-websites-and-apis-2c0h) (#webdev, 0 comments)

Notice the comment counts. A "what do you use" question on DEV often gets two to four answers, not forty. That cuts both ways: less reach, but a thoughtful answer is easy to see.

Also notice that a question title doesn't make something an ask. Plenty of #showdev and #webdev posts open with "Looking for..." and turn out to be launches ("Looking for Bangladeshi newspapers and news sources in one place? I recently built..."). And many "X alternative" titles in #webdev were reviews and SEO pieces, not requests. Read the body before you reply.

---

## Why the comments matter more than the posts

I read the full comment trees on three of the most-commented #discuss posts of the week (151 comments in total) using `/api/comments?a_id=ID`.

- **[I Tested 6 Best Web Scraping APIs So You Don't Waste Your Time](https://dev.to/startupcafe/i-tested-6-best-web-scraping-apis-so-you-dont-waste-your-time-27de)** (42 comments): 9 comments compared tools, pricing at higher volume or failure behaviour. This is the pattern you want: a comparison article whose readers pile in with what they use and what broke.
- **Two AI-agent essays** (57 and 52 comments): mostly opinion and agreement. Only 5 comments between them matched my tool keywords, and some of those were other builders mentioning their own products.

So the useful unit on DEV is often a write-up in your category (a comparison, a migration story, a "how we handled X" post) plus its comments. People who reply "we hit the same thing, we're evaluating a hosted option" are more qualified than most top-level posts.

---

## Copy-paste: tags and API calls to watch

All of these are public GET requests. The [Forem API docs](https://developers.forem.com/api/v0) say "all requests must send a user-agent header," so set one.

**Newest posts in a tag (the workhorse):**

```
https://dev.to/api/articles/latest?tag=discuss&per_page=100
https://dev.to/api/articles/latest?tag=help&per_page=100
https://dev.to/api/articles/latest?tag=showdev&per_page=100
```

**Popular posts in a tag from the last N days:**

```
https://dev.to/api/articles?tag=devops&top=7&per_page=100
```

**The full comment tree for one article** (replies are nested inside `children`):

```
https://dev.to/api/comments?a_id=<article id>
```

**Then filter titles locally** for phrases like these:

```
what do you use
how do you handle
how do you manage
alternative to
looking for a
recommend
anyone using
switched from
moving off
is there a tool
```

A note on search. There's a documented `/api/articles/search?q=` endpoint, but in my tests it matched loosely: `q=kubernetes` returned six recent articles of which one was tagged #kubernetes, and `q=alternative to` returned popular posts that didn't contain the phrase in their titles. The search box on the site is powered by Algolia and is fine for manual looks. For anything repeatable, pull a tag feed and filter it yourself.

**Rate limits.** The docs publish limits only for writes: "10 requests per 30 seconds" to create an article and "30 requests per 30 seconds" to update one (checked Nov 21, 2026). Read limits aren't documented. I made about 25 read calls spaced 4 to 6 seconds apart and got no 429s. If you script this, keep that pace and back off on any 429.

**A sensible watch list for a devtool:**

1. #discuss, every day, filtered by the phrases above.
2. #help, weekly (it's tiny).
3. Your topic tags (#devops, #security, #testing, whatever fits) with `top=7`, to find comparison and migration write-ups worth reading the comments on.
4. #showdev, weekly, for competitor launches and the questions people ask under them.

---

## How to reply on Dev.to without getting flagged

DEV's [Code of Conduct](https://dev.to/code-of-conduct) (last updated July 31, 2023) doesn't have a spam clause as such, but it lists "following our AI Guidelines and disclosing AI assistance if used to create content" as expected behaviour, and the [terms](https://dev.to/terms) let DEV "restrict any user's ability to participate on the platform at its sole discretion." The [AI guidelines](https://dev.to/guidelines-for-ai-assisted-articles-on-dev) are specific: "we ask that you not use bots or AI to generate comments on posts."

What I'd do:

1. **Answer the question as asked.** If someone asks how teams watch multiple coding agents, describe the approaches (logs, dashboards, sandboxes), name a few tools including ones that aren't yours, and say when each fits.
2. **Disclose in one line if you mention yours.** "I work on X, so grain of salt" is enough. Undisclosed self-mentions read badly once someone notices, and someone usually does.
3. **Write your own comments.** Draft with whatever helps, but a human should write and post the final reply. DEV asks for that explicitly.
4. **Don't drop a bare link.** A comment that's just your URL adds nothing and invites a flag.
5. **Follow up.** On a thread with three comments, you can have a real back-and-forth with the person asking. That's the advantage of low volume.

---

## How to write a #showdev post that doesn't get flagged

The rules that apply, checked November 21, 2026:

- **#showdev's guidelines:** "community-driven and not overly corporate or salesy." It's "really for projects," not for sharing tutorials you're proud of.
- **Terms, content policy:** posts must not be "designed primarily for the purposes of promotion or creating backlinks"; they "must contain substantial content" rather than just linking out; affiliate links must be "clearly disclosed."
- **AI-assisted articles** (last updated April 8, 2024) must disclose AI use in the post, "be checked for factual accuracy," and must not "promote any business, program, or course (including your own)." So if AI helped write a launch post, that post has a problem under DEV's own rules. Write launch posts yourself.

A structure that fits those rules:

1. **Title says what it is and who it's for.** "I built a CLI that diffs Terraform plans across workspaces" beats "Introducing AcmeCloud."
2. **Open with the problem you hit,** in a paragraph, with specifics.
3. **Show how it works:** a code sample, a screenshot, the architecture, the trade-offs. This is the "substantial content" the terms ask for.
4. **Be honest about limits.** What it doesn't do yet, what it costs, whether it's open source.
5. **Ask a real question at the end** ("how are you handling this today?") and answer every comment.
6. **One link to the project,** not five.

One more number to set expectations: 88% of #showdev posts in my week got zero comments. A launch post isn't a distribution plan on its own. Answering other people's questions for a few weeks first is what makes your launch post get read.

---

## Where Dev.to fits next to GitHub, Stack Overflow and the rest

DEV is best for context: write-ups explain the stack, what failed and what people tried. It's weak for urgent, specific asks, which tend to land in GitHub issues or Stack Overflow. For those, see [GitHub issues lead generation for devtools](https://useneedle.net/blog/github-issues-lead-generation-for-devtools), the [GitHub customer discovery guide](https://useneedle.net/guides/github-customer-discovery) and the [Stack Overflow customer discovery guide](https://useneedle.net/guides/stack-overflow-customer-discovery). If you plan to reply inside other projects' issue trackers, read [the maintainer-friendly GitHub issues guide](https://useneedle.net/blog/dev-tool-gtm-github-issues-maintainer-friendly) first. For a different developer crowd, the [Lemmy guide for founders](https://useneedle.net/blog/lemmy-for-founders-find-users-2026) covers the programming and self-hosting communities there.

If you'd rather not run these feeds yourself, [Needle's Dev.to page](https://useneedle.net/platforms/devto) explains how we search DEV articles and the comment threads under the most-discussed matches through the public API, and leave the replying to you. A cron job against `/api/articles/latest` does the same basic job for free if you're comfortable filtering the results by hand.

---

## Evidence notes

All checked **November 21, 2026**.

- Post counts and comment stats: `https://dev.to/api/articles/latest?tag=<discuss|help|showdev|webdev>&per_page=1000` (pages 1 to 3), counting posts published Nov 14 00:00 to Nov 21 06:20 UTC. #webdev's 3,000 fetched posts covered Nov 16 11:42 to Nov 21 06:18 UTC, so its figure is a daily rate, not a full week. Cross-check: `https://dev.to/api/articles?tag=<discuss|help>&top=7&per_page=1000` returned 603 and 13.
- Comment threads: `https://dev.to/api/comments?a_id=` for articles 5067508, 5058432 and 5007369. "Tool comments" were counted by keyword match plus reading, so treat them as approximate.
- Search tests: `https://dev.to/api/articles/search?q=` with `kubernetes`, `feature flags`, `alternative to`, `looking for a tool` and `what do you use`.
- API documentation: [Forem API v0 docs](https://developers.forem.com/api/v0) (user-agent requirement, write rate limits) and [v1 docs](https://developers.forem.com/api/v1) (articles, search and comments parameters). No read rate limits are documented in either.
- Forem: [forem/forem README](https://github.com/forem/forem).
- Tag guidelines: [#discuss](https://dev.to/t/discuss), [#help](https://dev.to/t/help), [#showdev](https://dev.to/t/showdev).
- Rules: [DEV Code of Conduct](https://dev.to/code-of-conduct) (updated July 31, 2023); [DEV terms](https://dev.to/terms) (no date shown); [Guidelines for AI-assisted Articles on DEV](https://dev.to/guidelines-for-ai-assisted-articles-on-dev) (updated April 8, 2024), originally announced in [this DEV Team post](https://dev.to/devteam/guidelines-for-ai-assisted-articles-on-dev-17n6).

## FAQ

### Can I promote my product on Dev.to?

Yes, in the right format. The #showdev tag exists "for showing off projects and launching products," but asks that posts be "community-driven and not overly corporate or salesy." DEV's terms say posts must not be "designed primarily for the purposes of promotion or creating backlinks," and AI-assisted articles may not promote any business "including your own."

### Does Dev.to have a public API?

Yes. DEV runs on Forem, and the Forem API lets you read published articles and comments without an API key, for example /api/articles/latest?tag=discuss and /api/comments?a_id=ID. The docs say every request must send a user-agent header. Writing, such as creating articles, needs an API key.

### What is the Dev.to API rate limit?

The Forem docs only publish limits for writes: 10 requests per 30 seconds to create an article and 30 per 30 seconds to update one. Read limits aren't documented. I spaced my read calls 4 to 6 seconds apart and got no 429 responses, but back off and retry if you do get one.

### Which Dev.to tags show people asking for tools?

#discuss is the main one: its guidelines say posts "should include a question, prompt, or topic that initiates a discussion." #help is for specific problems and is low volume (13 posts in the week to Nov 21, 2026). Topic tags like #webdev are huge but are mostly tutorials and launches.

### Does Dev.to allow AI-generated posts?

Yes, if you disclose it. DEV's Guidelines for AI-assisted Articles (last updated April 8, 2024) require disclosure in the post, fact-checking, and no promotion of any business, including your own. DEV also asks members not to use bots or AI to generate comments.

---

From Needle (https://useneedle.net). HTML version: https://useneedle.net/blog/find-developers-asking-for-tools-devto
