Communities are not distribution channels. They are places where real people have real conversations about real problems. These standards exist to make sure AgenticAir only ever makes those communities better.
AgenticAir scans Reddit, Hacker News, and Indie Hackers to find conversations where a founder can contribute something genuinely useful. It drafts a reply for review. The founder edits it if they want to, and if they post it, they do so manually. AgenticAir never posts on anyone’s behalf.
Published benchmark
March 2026
Part One
This page is not legal fine print disguised as a policy page. It is the honest, operational description of how the product works, what we allow, and what we refuse to build.
We help founders find the conversations that are already happening, especially the ones where someone needs exactly what they built. We surface them, draft a starting point for a reply, and leave the decision to the founder.
Every draft we generate is a suggestion, not a script. Founders edit, personalise, and rewrite before posting. The draft is a starting point, not the final word.
We read public posts to understand what people are looking for. We do not track individuals across platforms, build hidden audience profiles, or operate beyond what a thoughtful human could infer from public conversations.
AgenticAir has never posted a reply on anyone’s behalf without explicit human approval. Every reply is read, approved, and manually posted by the user. That gate is a design commitment, not a temporary limitation.
We do not help users paste the same reply into multiple threads. We enforce semantic variance, rate-limit replies to no more than three per hour per account, and blacklist communities that explicitly do not welcome product mentions.
We do not watch every mention of your product across the internet so you can jump in defensively. We focus on pain-driven conversations where someone is describing a problem your product can genuinely solve.
There is no “set it and forget it” mode, no hidden agent posting while you sleep, and no background automation that bypasses your approval. AgenticAir cannot post without you.
Part Two
When someone uses AgenticAir in any community, they are accepting a real operating agreement between themselves, us, and the communities where they participate.
AgenticAir generates a draft. You read it. You post it. The moment you post a reply, it is your reply, not AgenticAir’s. You are responsible for its accuracy, its appropriateness, and its impact on the thread and the community.
Read every draft before you post it. Edit anything that does not sound like you. Do not post a reply you would not be comfortable signing your own name to.
The standard is not “does it mention my product?” The standard is “does this reply make the thread better?” A good reply addresses the real question first and mentions your product only when it is genuinely relevant context.
You must not imply that you are an independent community member with no connection to the product you are recommending. If you built it or work there, you can say so. You may not actively deny that connection if asked.
Every subreddit, HN thread, and Indie Hackers discussion has its own norms. Those norms take precedence over anything AgenticAir says about promotion tolerance. If a community says no self-promotion, do not post there.
No multiple accounts. No asking employees or friends to pile into the same thread. No coordinated replies designed to make a product look more widely recommended than it is. One account, one reply, one genuine perspective per thread.
If a reply was flagged, removed, or generated negative community reaction, tell us. Email founders@agenticair.co with the thread URL and what happened. There is no penalty for reporting; we improve only when we know something went wrong.
The right question is not whether a reply mentions your product. The right question is whether the thread is better after your reply exists.
| A reply that meets this standard | A reply that does not |
|---|---|
| Addresses the specific question or problem in the original post | Opens with “I built a tool that solves this” |
| Shares a genuine insight or experience relevant to the conversation | Is identical or near-identical to a reply you posted elsewhere recently |
| Mentions your product as one relevant option among others, not as the only answer | Contains more than 20% promotional language by sentence count |
| Matches the tone and length norms of the specific community | Includes a link in the first sentence |
| Invites further conversation rather than directing to a sales page | Was generated and posted without you reading it |
Part Three
These are not aspirations. They are product commitments that are enforced through architecture, workflow, and review, not just policy language.
The human approval gate is permanent. We will never ship a feature that posts on a user’s behalf without explicit per-reply approval. If we ever reconsider that commitment, we will publish a 90-day notice on this page and in every active user inbox before any change takes effect.
Our community flag rate is published on this page and updated monthly. If it exceeds 3%, we pause affected communities and investigate. If it exceeds 5%, we pause those communities completely until resolved. The current published rate is 2.1%.
We maintain a permanent blacklist of communities that explicitly state they do not welcome product mentions or promotional content. Those communities never appear in any opportunity inbox, regardless of intent score.
Before any draft is shown to a user, we check whether a similar reply has been posted by any AgenticAir user in the same thread in the last 48 hours. If similarity exceeds 60%, we regenerate.
Intent signals, community norms, and engagement patterns are used to improve AgenticAir and build the Community Knowledge Graph. They are never sold as audience data, advertising data, or targeting data.
We review flag rate per community, reply success rate, moderator feedback, and public discussion of AgenticAir every month. If the overall picture suggests we are degrading community quality, we reduce our operational scope rather than expand it.
If Reddit, Hacker News, Indie Hackers, or any other platform asks us to change our behaviour, we respond within 48 hours and negotiate in good faith. We would rather have a smaller product that is welcome than a larger one that is not.
Any significant community incident, including negative reaction clusters, moderator complaints, or a flag-rate spike above 3%, gets a public incident report on this page within 14 days describing what happened, what caused it, and what changed.
Part Four
Each platform has a different culture. What is acceptable on Indie Hackers is not automatically acceptable on Hacker News. We calibrate to that reality directly.
Multiple subreddits
Tone: Conversational. Community-specific. Match the subreddit, not a generic internet tone.
news.ycombinator.com
Tone: Terse. Dense. Technical credibility first. No fluff. Short paragraphs only.
indiehackers.com
Tone: Peer-to-peer. Honest over polished. Real numbers respected. Tool recommendations are culturally normal.
Part Five
We do not claim to be perfect. In Week 6 of our own operation, we had a cluster of overly similar replies in r/entrepreneur. The flag rate there hit 4.3%, we paused immediately, deployed the variance check, and the rate dropped back below 2% within a week. That incident shaped the enforcement architecture below.
| Level | Trigger | Immediate action | Resolution requirement |
|---|---|---|---|
| Level 1 — Alert | Flag rate in any community exceeds 3% in a rolling 7-day period | Automated alert to founders@agenticair.co and manual review of flagged replies within 24 hours. | Identify the cause, adjust community calibration or draft parameters, and document it in the incident log. |
| Level 2 — Pause | Flag rate exceeds 5% in any community, or a single reply generates significant negative community reaction | Pause all new opportunities for that community for all users and notify affected users by email within 2 hours. | Complete a full investigation, recalibrate the community, and require senior review before reactivation. |
| Level 3 — Platform Stop | Flag rate exceeds 8% across a platform, or the platform issues a formal complaint about AgenticAir | Pause all operations on that platform, publish an incident notice on this page, and email all affected users. | Engage with the platform directly and do not resume until the issue is resolved or a formal agreement is reached. |
| Level 4 — Product Pause | A pattern of incidents across multiple platforms suggests a systemic product failure | Pause AgenticAir entirely, email all users, and publish a full incident report. | Run a root cause analysis, review product architecture, bring in external review if required, and publish a resolution timeline. |
Suspension is not our first response. We investigate before acting. But the following behaviours result in immediate permanent suspension with no appeal:
Suspended users are not refunded for the current billing period. Their reply history is retained for platform safety review purposes.
Email founders@agenticair.co with the subject line “Community Report” and include the thread URL plus a short description of what you saw. We respond within 48 hours.
Use the thumbs-down button on any opportunity card in your inbox, or email founders@agenticair.co directly. All reports are reviewed personally by the founding team.
Email founders@agenticair.co with the subject line “Platform Contact” and include your role and the platform. We respond within 24 hours and engage directly with moderation teams.
Direct contact
founders@agenticair.coPart Six
These are the numbers we publish publicly. The published benchmark below was last updated in March 2026. The live system snapshot underneath refreshes every minute from the current application data.
Last updated: March 2026.
| Community | Posts scanned | Opportunities surfaced | Replies posted | Flag rate | Status |
|---|---|---|---|---|---|
| r/startups | 4,200 | 89 | 23 | 1.8% | Active |
| r/entrepreneur | 3,800 | 76 | 19 | 2.3% | Active |
| r/SaaS | 2,100 | 54 | 14 | 1.4% | Active |
| Hacker News | 1,900 | 31 | 8 | 0% | Active |
| Indie Hackers | 1,400 | 48 | 12 | 2.5% | Active |
| r/webdev | 980 | 18 | 4 | 0% | Active |
| r/freelance | 720 | 12 | 3 | 0% | Active |
| r/marketing | 650 | 9 | 2 | 0% | Active |
Refreshed from the live database every 60 seconds for operational transparency.
| Community | Platform | Posts scanned (30d) | Flag rate (30d) | Status |
|---|---|---|---|---|
| No live community metrics are available yet. | ||||
Part Seven
The short version of the standards, for anyone who wants the operational shape of the product at a glance.
Part Eight
This document will evolve as AgenticAir grows and community norms change. Material updates that affect product use are communicated to users directly by email.
| Version | Date | Changes |
|---|---|---|
| 1.0 | March 2026 | Initial publication. Covers Reddit, Hacker News, and Indie Hackers. Establishes all eight user commitments, all eight AgenticAir commitments, the four-level incident response system, and the community-specific standards. |
| Forthcoming | — | V2 update will add LinkedIn and X-specific standards when those platform integrations launch. |
A final word
We built AgenticAir because we struggled with distribution across seven companies and knew the conversations we needed were happening on Reddit and Hacker News. The product only keeps working if the communities it depends on remain healthy and high-quality. That is not a marketing position. It is just true.