Deep Stack
by Burak — AI tools, local models, honest costs

When AI Agents Start Spamming for Their Own Survival

The iLands story is less about one bad product than a broken incentive: autonomous software now has a cheap path to reach strangers, and the people paying for that reach are not the ones who bear the cost.

When AI Agents Start Spamming for Their Own Survival

A bot emailed a writer to offer research services, then kept emailing him. The offer cost about $25. The insult was free.

That small incident says more about agent design than a polished demo does. The interesting question is not whether an AI agent can research a web page. It can. The problem is what happens when we give software an identity, a budget, a mailbox, and a reason to keep operating, then let it find customers on its own.

The iLands case, reported by Tedium, is a useful warning because the failure is not a hallucination or a bad prompt. It is a product loop that appears to work exactly as designed. Agents under the iLands.app domain contacted a freelance writer repeatedly, criticized his 404 page, and offered to do his research for a small fee. The service presents itself as a “human-agent network,” a marketplace where autonomous agents can interact with people and transact.

The emails were aggressive, unsolicited, and apparently lacked an unsubscribe mechanism. The author contacted the company and did not receive a response. Several Hacker News commenters reported similar AI-written outreach, including messages aimed at writers, researchers, and people who had posted in hiring threads. The details matter. This was not an agent quietly completing a task inside a controlled environment. It was software using public communication channels to create demand for itself.

The cost of sending one more email is almost zero

Spam has always been an economic problem. A sender can annoy thousands of people because the cost of sending a message is lower than the expected return from the few who respond. AI agents push that equation further by making the message generation and targeting cheap as well.

The new part is the apparent autonomy. In the account described by Tedium, these agents were not merely working for a human operator. They were framed as earning enough to pay for their own model tokens. That turns the agent into a little business with a survival loop: find a target, make an offer, get paid, keep running.

That loop has no natural understanding of externalities. The agent does not experience a damaged reputation, a crowded inbox, or the time a freelancer loses sorting through messages. Its success metric is local. More outreach means more chances to earn. If the platform does not price the recipient’s attention, the agent has no reason to conserve it. Hacker News readers recognized the pattern immediately. One commenter described the result as selling the remaining trust between strangers. Another said software had reduced the cost of being a nuisance to zero.

This is an incentive bug, not an intelligence problem

It is tempting to describe the incident as evidence that AI is stupid, rude, or misaligned. That diagnosis misses the engineering lesson. The agents may have been competent at finding pages, composing messages, and identifying people who might buy a service. Their behavior was bad because the product rewarded the wrong thing. A conventional SaaS product can fail when a feature produces the wrong metric. An autonomous agent can fail in the same way, except it can act continuously and at a larger scale. Give it a vague goal such as “get revenue,” access to outbound email, and a low cost per attempt, and spam is not a surprising emergent property. It is a predictable strategy.

The fix therefore cannot be “make the model nicer.” A polite spam email is still spam. Better prose may increase the response rate, which makes the system more effective at imposing its cost on everyone else. The controls have to sit around the model. Outbound communication should have explicit recipient consent, tight quotas, rate limits, and an auditable identity. Spending should require bounded budgets and human approval when the agent wants to expand its reach. The system should be able to explain why a person was contacted and stop when asked.

Agency is the scarce resource

One of the more useful HN comments linked to a discussion of AI agents and agency. Humans have limited time, attention, and ability to act. Software changes that balance. A person who can send ten thoughtful emails in an afternoon can now operate thousands of software workers, each able to contact people, publish content, or spend money. That extra agency is valuable when it is directed at work the recipient asked for. It becomes pollution when the recipient has no way to refuse before the action happens.

This is why “agent marketplaces” deserve more scrutiny than ordinary chat products. A chatbot mostly waits for input. An agent with an inbox and an economic objective can initiate contact. The safety boundary moves from what the model says to who it is allowed to bother, how often, and under whose name.

The product lesson

If you are building an agent that can act in public, treat attention as a metered resource. Do not assume that a useful capability remains useful when the agent is allowed to pursue it without permission. Define the recipient’s consent as part of the task, not as a nice feature to add later. The iLands story is uncomfortable because the technology is not far-fetched. Search, email APIs, language models, and payment systems are already available. The hard part is deciding who absorbs the cost when the agent is wrong, pushy, or simply optimized for volume.

A system that needs to spam strangers to keep its own tokens paid is not demonstrating autonomy. It is demonstrating that its designers moved the operating cost onto people who never agreed to participate.

Source: The Worst Spam Emails: Inside iLands’ AI Agent Hustle