X has recently implemented restrictions on programmatic replies via its API specifically to combat automated reply spam, particularly from AI and LLM-generated content. This change was announced by the official X Developers account and detailed in their developer community forum.
Programmatic replies using the POST /2/tweets endpoint are now restricted. You can only post a reply via the API if the original post’s author explicitly invites/engages with you by: Mentioning your account in their post, or Quoting your post. If neither condition is met, API attempts to reply will be blocked.
Regular (non-reply) tweet and post creation via the API remains unchanged and fully supported. This applies to Free, Basic, Pro, and Pay-Per-Use API tiers; Enterprise and Public Utility apps are exempt.
The goal is to reduce low-quality, automated “spam” replies often AI-generated “slop” that flood conversations under popular posts, improving overall discussion quality on the platform. This follows earlier efforts by X to curb bot spam and manipulative engagement, including prior restrictions on reward-based posting apps (“InfoFi”) in January 2026 that also targeted AI-driven reply spam.
Register for Tekedia Mini-MBA edition 19 (Feb 9 – May 2, 2026).
Register for Tekedia AI in Business Masterclass.
Join Tekedia Capital Syndicate and co-invest in great global startups.
Register for Tekedia AI Lab.
Many users and developers appear to welcome the move, describing it as a step against bot-heavy, low-effort replies that degraded experiences under viral threads. Manual replies; typed by users themselves are unaffected—only automated and programmatic ones face these new limits.
The recent restriction on programmatic replies via the X API primarily targets automated, low-quality, and AI-generated (“LLM slop”) reply spam that has plagued threads under popular posts. This builds on earlier 2026 efforts, like banning “InfoFi” reward-based apps in January that incentivized bot-driven engagement.
Automated bots and AI tools can no longer flood conversations with instant, repetitive, or irrelevant replies like crypto promotions, fake accounts mimicking celebrities, generic “gm” bots, or low-effort AI comments. This should noticeably clean up threads under viral posts, making discussions more authentic and higher-quality.
Many users and observers describe the change as a welcome fix to a “plague” of degraded timelines. Expect fewer irrelevant or spammy replies appearing seconds after a post goes live, leading to better engagement in genuine conversations.
Broader Anti-bot Momentum
This follows prior crackdowns and is seen as a step toward restoring discussion integrity on X. Major disruption for automated reply tools: Bots, AI assistants, monitoring apps, customer service bots, or any service relying on programmatic replies to non-engaged posts are now blocked unless the original author explicitly mentions the replying account or quotes its post.
This kills most unsolicited auto-reply use cases on Free, Basic, Pro, and Pay-Per-Use tiers. Developers are questioning edge cases, like whether an account can programmatically reply to its own posts; not explicitly addressed in the announcement, but likely still restricted if it doesn’t meet the summon criteria.
Some see this as another layer of restriction following API paywalls and InfoFi bans, potentially limiting creative or legitimate uses like community tools or moderated bots. However, non-reply posting via API remains fully supported, so tweet scheduling, publishing, etc., are unaffected.
Projects depending on broad reply automation must pivot—e.g., shift to manual engagement, wait for mentions and quotes, or explore alternatives outside X’s API. Developer community discussions focus on clarification rather than heavy backlash so far, with some appreciating the spam relief despite the hit to flexibility.
No widespread reports of immediate massive disruptions beyond spam bots going quiet, but long-term effects on third-party tools and crypto and Web3 integrations already hit hard earlier in 2026 could emerge. This appears to be a net positive for regular users tired of spam-filled replies, while forcing automated services to rethink strategies.
The change is live now, so impacts on reply sections should become visible quickly in high-engagement threads.