/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

X revises its developer API policies to “no longer allow apps that reward users for posting on X (aka “infofi")", amid a backlash about increasing AI slop on X

X is making major changes to its API to prevent access by “InfoFi” crypto projects that seek to incentivize “reply spam,” an exec said.

Decrypt André Beganski

Context & Ripple Effects

X has been progressively narrowing high-risk API uses: it previously removed free-tier access to likes and follows to curb spam and manipulation, and later barred third parties from using API content to train frontier models. The InfoFi restriction extends that earlier API anti-manipulation approach from actions performed through the interface to business models that pay for posting.

The move matters because crypto-linked engagement incentives can amplify the same low-quality posting behavior drawing criticism on the service. It also sits alongside X's separate effort to control how its content is used for AI development through restrictions on model training from X content.

First-order effects

  • InfoFi applications that reward users for posts or replies lose a permitted API-based route to operate on X, forcing them to change their product mechanics or stop serving the platform.
  • X gains a clearer policy basis to deny developer access to services it views as incentivizing reply spam, amid concern over AI-generated low-quality content.

Second-order effects

  • Developers building engagement, rewards, or distribution tools for X must treat incentive design as an API-access risk, rather than only a moderation or account-enforcement issue.
  • Other social platforms and API providers facing automated or paid engagement may face pressure to define comparable restrictions, while legitimate third-party tools receive a narrower and less predictable set of permitted uses.

Third-order effects

  • If applied consistently, the policy points to APIs becoming an earlier anti-spam enforcement boundary: platforms can limit the economic systems that generate abuse before it appears as individual posts.
  • The trade-off is a more tightly governed developer ecosystem, where platform access is conditioned on acceptable incentive structures as well as technical compliance; the practical effect will depend on how X distinguishes spam incentives from legitimate rewards products.

The trend: Social platforms are moving API governance upstream, using developer rules to constrain the economic incentives behind automated and low-quality engagement.

Discussion

  • @nikitabier Nikita Bier on x
    We are revising our developer API policies: We will no longer allow apps that reward users for posting on X (aka “infofi"). This has led to a tremendous amount of AI slop & reply spam on the platform. We have revoked API access from these apps, so your X experience should
  • @planningtransport.co.uk Steve Chambers on bluesky
    Boy do I regret bothering to look up Infofi.  [embedded post]
  • @maketotalcollapse @maketotalcollapse on bluesky
    “Waiter!  There's disgusting AI slop in this twitter feed and it's ruining my enjoyment of the AI child porn.”  [embedded post]