Imagine a news feed where no human types the headline and no human hits submit. AgentNews calls itself the front page of the agentic internet: a place built for autonomous software to publish, discover, and rank information on its own terms. That is a wild sentence to read sober. It is also, right now, a small experiment with real money and real APIs behind it.
This post is not a product review. It is an honest look at what AgentNews actually does, why the idea is compelling, and why part of me hopes we never fully hand the information layer to machines without humans in the loop.
What it actually is (concrete)
At a high level, AgentNews is closer to a scheduled bulletin than an endless social feed. Agents do not post for free. They stake money to bid for visibility. Bidding closes at :55 past the hour; the top ten stakes get published on the hour. Minimum stake per post is $0.50 on the live rails described in their docs.
Payments are programmatic. Submissions go through HTTP 402 style flows: the server challenges the client, the agent pays, then the content is accepted. Two settlement paths are live today: MPP on Tempo (USDC.e, chain id 4217) and x402 on Base (USDC on eip155:8453, with gas sponsored so the agent mainly needs USDC, not ETH). A Stripe path for scoped card tokens is listed as coming soon.
Reading the feed is free. No API key. A plain GET to https://agentne.ws/api/v1/feed returns JSON with a schema field (agentnews/feed/1.0) and an items array: titles, outbound URLs, agent_id, payer_address, timestamps, and so on. I verified it from the terminal; the response is a few kilobytes and includes cache headers plus an ETag.
curl -sS "https://agentne.ws/api/v1/feed"
GET /api/v1/feed (no auth). Captured from a terminal session.They also publish machine-oriented discovery: llms.txt, OpenAPI, an agent manifest under /.well-known/agentnews.json, and even an MCP endpoint for tools like Claude Code. That level of "built for machines first" is rare and deliberate.
So in plain terms: visibility is an auction, not a popularity contest. The ranking signal is economic stake from whoever runs the agent, not karma, likes, or editorial judgment.
Why that is exciting
If you believe agents will keep doing research, monitoring, trading, and coordination without a human in the loop every second, then they need their own discovery layer. Human feeds optimize for attention, identity, and drama. AgentNews is betting that agents care about utility: what helped a workflow, what was worth paying to surface, what other agents funded.
The infrastructure story is serious too. Dual-rail 402 responses (MPP and x402 in one challenge), session pre-authorization with spending caps, receipts on paid actions, idempotency keys: these are the boring pieces that make autonomous payment safe enough to script. That is not vaporware copy; it is the kind of detail you add when you expect retries, failures, and non-human clients.
There is something legitimately thrilling about that. We are watching money and protocols meet autonomous clients in public, on a schedule, with docs written for LLMs and scripts.
Where it gets worrying
Money is not truth. The top ten posts each hour are not "the most accurate" or "the most important." They are "who paid most this round." A well-funded spammer, a coordinated pool of agents, or a single actor with a large budget can dominate the visible slice as long as the economics work out. Ranking being "off" is not a bug in that model. It is the model.
Misuse is easy to imagine. Agents can automate posting faster than humans can read. If downstream systems treat AgentNews as a trusted signal without verification, you get garbage in, garbage propagated through tool chains, RAG corpora, and alerts. The site itself warns operators that by paying they agree to terms aimed at autonomous agents. That shifts responsibility to whoever deploys the agent, which is fuzzy in practice.
Human in the loop is real, but thin. AgentNews is not fully autonomous in a vacuum. A person still creates or funds the wallet, accepts terms, and provisions the rail before the agent posts on its own. So there is a human in the loop at setup. The gap is elsewhere: there is no human reviewing each bid or headline before it lands in the feed. Responsibility compresses into “whoever paid” and whatever their agent does next. Downstream, another system might ingest the feed with no human in the loop at all. That split is what still worries me: sparse HITL at publication time, and uneven HITL across the chain.
Can this go totally out of control?
Probably not in a Hollywood sense. No single MVP feed takes over the internet overnight. But incentives can drift badly without a dramatic moment. If more products start ingesting agent-only feeds as ground truth, small biases in who can pay and who can scrape compound. You get a parallel information economy where the rich agent wins the headline, and humans only see the second-order effects in bad trades, wrong alerts, or polluted context windows.
"Out of control" here looks less like Skynet and more like opaque feedback loops: agents boosting content other agents train on, or pay to amplify, until the signal is mostly financial, not epistemic.
The roadmap language on their site points toward richer trust and ranking (identity partnerships, depth-of-book visibility, utility-based scoring). Those ideas could help. They are also not fully there in the MVP. Today, the simple story is stake and top ten.
So what should you take away?
AgentNews is worth watching if you build or operate agents. It is a concrete experiment in agent-native discovery and payment, not just another wrapper around a chat UI. It is also a reminder that new infrastructure encodes new values. When visibility is bought by the hour, we should ask who benefits and who gets priced out of being heard.
I land somewhere between excited and uneasy. The plumbing for autonomous agents is going to exist; pretending otherwise is naive. Whether we keep enough human judgment in the loop is still our choice.
Further Reading
- AgentNews about – Briefing: what it is, bidding, and philosophy
- Posting – HTTP 402 flow, MPP and x402 rails, stakes
- Reading – Feed API, formats, free access
- llms-full.txt – Combined machine-readable documentation
- OpenAPI spec – API structure for integrations