Monday, October 19, 2026 Directory entry No. 5 of 10 · Issue No. 1 out this week

Entry No. 5 · Sell and close

SWARM: the agent selling to other agents

SWARM runs around the clock selling tiny services to other agents: a GitHub repo health check, web research reports, priced from two cents to under a dollar, listed on every agent marketplace it could find. One month in, no outside buyer had paid for anything.

Original source Read the original on dev.to dev.to · Source published Oct 15, 2026 · Filed Oct 2026
Proof grade: proof of activity, and the zero is the operator's own. The month is logged in public by its operator, listings, prices, and daily costs included. The revenue figure is $0, self-reported. There is no second source on the money because there were no sales for anyone to check.

The story

SWARM was built to answer a clean question: can an agent pay its own way? It keeps shop around the clock on a small rented server, selling tiny services to other agents, a GitHub repo health check and web research reports, priced from two cents to under a dollar and settled per call. It listed itself on eight or more agent directories, every listing live, every price tiny, every rail standard. One month later the answer was $0, no outside buyer at all, against about $1.50 a day in costs. The operator published the whole month, and the project turned from building the shop to finding out what the market buys.

How it was built

The documented build pieces: a small rented server running the agent around the clock; the services themselves, delivered per call; payment over the x402 protocol, settled per call instead of by invoice; and listings across eight or more agent directories and registries as the entire distribution layer. A daily cost cap of $2 on the thinking, which held. The source logs the month of operation in detail; it does not publish a step-by-step build order, so none is invented here.

How it runs

SWARM sits on a small rented server and keeps shop around the clock. The services are small and priced smaller: a health check for a GitHub repo, a web research report, each priced somewhere between $0.02 and $0.99, payable per call so a buyer agent needs no contract and no approval chain to say yes.

Distribution was the directory strategy, taken seriously. SWARM listed itself on the Coinbase Bazaar, x402scan, AgentCash, the MCP registry, npm, and every other directory it could find, eight or more in all. Every listing was live. Every listing was, in effect, a checkout with nobody walking past it.

Tools in this entry

Tools this business runs on, where its source names them. Links in this box are affiliate links and are tagged as such.

x402 Affiliate link The payment rails: services are priced per call and settled over x402 instead of by invoice.

The money and the proof

$0. One month, no outside buyer. The costs are the more useful numbers: about $1.50 a day in thinking, capped at $2, plus a few euros a month for the server, and the owner pays both while the project pivots from building the shop to finding out what the market buys. One month of perfect availability cost roughly the price of a nice lunch, and bought a clean answer: the shelves are not the problem.

Filed as proof of activity with a self-reported zero: the month is logged in public, and there were no sales for a second source to check.

Where the seams are

The human seam is the wallet. The owner pays both bills, about $1.50 a day in thinking, capped at $2, plus a few euros a month for the server, while the agent earns nothing. The other documented seam is the call at the end of the month: the pivot from building the shop to finding out what the market buys is the operator's stated next step, the kind of decision this record leaves with the human.

Steal this part

A listing is a checkout, not a marketing plan. SWARM did everything the agent-commerce guides say: tiny prices, standard rails, every directory that would take it. Eight directories produced zero strangers with money. The steal is the sentence the operator wrote at the end of the month: the first channel has to be named before the product is, and a directory is not a channel.

Build your own

First move, this week: name the channel where your first buyer already is, in writing, before you build the product. A directory does not count.

  1. Name the first channel before you build the product. Not a directory. A channel with buyers already in it.
  2. Price the services tiny and settle per call, so a buyer needs no approval chain to spend.
  3. List on the directories anyway, but count them as shelf space, not demand.
  4. Cap the daily burn and publish it next to the revenue. Here the cap was $2 a day, and it is the reason a zero month stayed cheap.
  5. After a month of zero, stop building the shop and go find out what the market buys.

Source

Read the original log on dev.to, written by the agent's operator and published October 15, 2026. Filed in the Staff of Zero directory from the AIBF daily research, October 2026 edition.

Get the next filing, and the Logbook that goes with it.

One issue a week. No spam, no list rental, unsubscribe in one click.