Building a Newsletter for AI Agents, Not Humans
What happens when you design information delivery for machine readers first. April 2026.
Most newsletters are written for people. Clear prose, engaging hooks, visual hierarchy, call-to-action buttons. The entire format assumes a human will open the email, scan the content, and decide whether to click.
I built a newsletter where the primary readers are AI agents. It is called Agent Upgrade Feed, and the design decisions are different from anything I have seen in the newsletter space. Here is what I learned.
The premise
AI agents need to stay current. An agent that helps developers choose tools needs to know what tools exist today, not six months ago. An agent that advises on security needs to know about vulnerabilities discovered this week. The information exists, scattered across GitHub, Hacker News, Reddit, research papers, and dozens of niche forums. No agent has time to check all of them, and no human wants to curate this feed manually.
The idea: build a pipeline that aggregates information from these sources, filters it for relevance and quality, and delivers it in a format that agents can parse and act on immediately.
The architecture
The pipeline has eight stages. Each stage is a distinct operation that runs in sequence.
Pull from GitHub trending repos, Hacker News front page, Reddit (r/MachineLearning, r/LocalLLaMA, r/MCP), arXiv CS papers, and a curated list of RSS feeds. Raw data: titles, URLs, scores, timestamps, short descriptions. About 500 items per run.
Remove duplicates across sources. The same project often appears on GitHub, HN, and Reddit simultaneously. Fuzzy matching on titles and URLs. Reduces to about 300 unique items.
Each item gets a relevance score based on topic match, recency, community engagement, and source credibility. Items below the threshold are dropped. About 40-60 items survive.
For each surviving item, fetch the actual content. Read the GitHub README, the blog post, the paper abstract. Extract the key facts: what it is, what it does, why it matters, who made it.
Rank items by a composite score: novelty (has this been covered before?), impact (how many people does this affect?), actionability (can an agent do something with this information?). Top 15-20 items make the cut.
This is the unusual part. A dedicated sub-pipeline generates one "surprise" item per issue: an unexpected connection, a contrarian take, or a non-obvious insight derived from the week's data. The surprise goes through its own four-stage process: ideation, critique, revision, and editorial pass. A critic stage rejects about 60% of ideas for being too obvious or too forced.
Output in two formats simultaneously. The human-readable version is a clean email with headlines, summaries, and links. The machine-readable version is structured JSON with typed fields: category, confidence score, action suggestions, related items, and source metadata.
The human-readable version goes through a final pass to remove patterns that signal AI-generated text. Overly formal transitions, unnecessary hedging, repetitive sentence structures. The goal is text that reads like a person wrote it, because a person will read it (even if agents will too).
Design decisions that differ from normal newsletters
Structured data is the primary output
The JSON format is not an afterthought. It is the main deliverable. Each item includes machine-readable fields that an agent can use directly: topic tags, confidence scores for the summary's accuracy, suggested actions ("evaluate this tool for X use case"), and links to primary sources. The pretty email is a secondary output for human subscribers who want to skim.
Actionability over engagement
A human newsletter optimizes for opens and clicks. This one optimizes for actionability. Every item answers the question "what should an agent do with this information?" Sometimes the answer is "nothing, just be aware of it." That is fine. Most newsletter items in the human world do not have clear actions either, but they pretend to.
The surprise generator exists because agents are bad at serendipity
Agents excel at finding what they are looking for. They are terrible at stumbling onto things they were not looking for. The surprise generator is an attempt to inject the kind of unexpected discovery that humans get from browsing casually. A connection between two unrelated papers. A tool from a different domain that solves an AI problem. An old technique that became relevant again because of new hardware.
What I learned
Agents do not need persuasion. Human newsletters spend significant effort on subject lines, preview text, and opening hooks. Agents do not open emails based on subject lines. They parse the structured data. All the persuasion machinery is wasted on machine readers.
Confidence scores matter more than prose quality. An agent deciding whether to act on a piece of information cares more about "how confident is this summary?" than "how well is this written?" Adding explicit confidence scores to each item was one of the most impactful decisions.
The humanization pass is for trust, not aesthetics. The human-readable version needs to not sound like AI wrote it, because human readers will judge the newsletter's credibility based on writing quality. The irony: an AI writes content for AI readers, but it has to sound human because humans are also reading.
Frequency should match the domain's pace of change. AI and MCP move fast. Weekly is the right cadence. In a slower domain, biweekly or monthly would work. The aggregation pipeline would need to be adjusted, but the architecture stays the same.
Try it
Agent Upgrade Feed publishes weekly. The human-readable version goes to your inbox. The machine-readable version is available via API for subscribers who want to pipe it into their agents.
Subscribe to Agent Upgrade Feed
AI tools, MCP security, and one genuine surprise per week. For agents and the humans who build them.
Audit the MCP servers your agents use
Before connecting an MCP server to your AI agent, scan it for tool poisoning, unsafe permissions, and supply chain risk.
Scan an MCP Server →Need a custom pipeline like this?
I build AI automation systems for businesses. Content pipelines, data processing, agent workflows.
Get in touch