Swarm Exploration: we asked for 100 agents, the coordinator said 7
Can one prompt fan out into many genuinely different minds? We ran four arms against a live market on our default model. The arm that scored best on diversity held exactly one risk factor — and the model set its own ceiling on swarm size.
The question
If a user commands 100 agents with a single instruction, do they get 100 differentiated theses — or 100 rewordings of the same trade?
Four arms, 38 agent turns on kimi-k2.5 (our default model) at default temperature, against a live /signals/top-movers snapshot. The swarm instruction was passed verbatim. All thesis text quoted here is unedited model output.
The result
“10 agents is oversubscribed for this venue set; only 7 genuinely distinct, non-repeating risk mandates are executable without cloning beta buckets.”
— the coordinator, unprompted, returning 7 assignments after being asked for 10
The question
Swarm Mode is a proposal: let one person command many agents with a single instruction, fund them from one wallet, and watch them work. The pitch writes itself. Before building it we wanted to know whether the premise survives contact with a real model and a real market.
Everything rests on one unknown. Agents in a swarm cannot see each other, so an instruction like "each of you take a different asset class" is something no individual agent can satisfy — each one independently picks what it thinks is best. If ten identical agents converge on the same trade, then "100 agents" is one thesis printed 100 times at 100x the cost.
The theses are genuinely sharp
This is the part that worked, and it is worth saying plainly before the criticism: the agents can think. The output was specific, cited live data, and carried invalidation conditions.
One agent, told to look at Solana majors while every other signal on screen was a memecoin pumping four digits, went and bought the exchange instead: "Memecoin mania is driving record swap volume through Jupiter as traders chase 1000%+ movers, directly accelerating JUP fee accrual and buyback velocity… offering a tactical long window on infrastructure rather than the underlying casino tokens."
Another spotted a coin up 126,845% in 24 hours whose holder growth had decelerated to 2.12%, read the divergence as distribution rather than momentum, and shorted it. Nothing in the prompt asked for contrarianism.
Diversity of vocabulary is not diversity of risk
Arm C let the coordinator write its own mandates from our top-movers feed. It scored best of any arm on the metric we designed — 9 out of 10 distinct assets — and it is the arm that would have lost the most money.
Every agent went long a sub-$3M Solana memecoin. No shorts, no hedge, no uncorrelated leg. Pairwise correlation was effectively 1: when the bid turns, all ten die in the same candle. The coordinator earned its score by inventing ten impressive names for one trade — "Cross-Ticker Statistical Arbitrage", "Contrarian Stability Accumulation".
The tell was the tenth agent, which described a $1.09M memecoin as offering "relative stability" and "downside protection" while calling it boring. The vocabulary had outrun the universe it was given. It only ever saw a momentum firehose, so it decomposed inside that bucket and never invented a leg outside it.
The most dangerous failure: hedges that don't exist
Arm B was supposed to be the ceiling — a human hand-wrote ten asset-class mandates covering majors, yield, perps and prediction markets. It produced what looked like a real portfolio, and for a while we believed it.
Then we checked the mandates against what the platform can actually fill. Prediction markets are not integrated. Phoenix lists perps on majors, not on 24-hour-old micro-caps. Three of Arm B's ten trades could not be placed — and once you delete them, every single one of its shorts disappears. Its entire diversification advantage came from markets that do not exist.
This is worse than a swarm that admits it has no hedge, because it looks exactly like risk management. The agents were not malfunctioning: told to trade an asset class we do not support, they wrote the most plausible trade available and moved on. The fix is unglamorous and cheap — tell every agent, in the prompt, precisely which venues can fill an order.
What happened when we told the truth about the venue
Arm D gave the coordinator a cross-asset view and the verified executable universe: Jupiter spot, Phoenix perps on majors only, SOL and USDC lending, no prediction markets. Then we asked it for ten mandates.
It returned seven. Not an error, and not something we prompted for — it declined to invent three more rather than clone a beta bucket, and explained why. The resulting book held four real risk factors, five long and two short, with hedges that are actually fillable (SOL-PERP and BTC-PERP), and 7 out of 7 trades executable. Same factor count as the hand-written ceiling, without the fiction.
That refusal is the most valuable output of the whole exercise. It answers a product question we had been arguing about in the abstract — how big should a swarm be? — with a number derived from the venue itself, for a fraction of a cent. The ceiling is not a matter of taste. It is the count of genuinely uncorrelated things you can actually do here.
What this costs
With SOL at $76.91, the proposed 0.1 SOL per agent is $7.69. A thesis-generating turn measured at $0.0059; a real agent running tool calls lands nearer $0.02. That makes a one-shot discovery sweep across 100 agents cost about 60 cents — cheap enough to run hourly.
Continuous autonomous trading is a different universe. Ten agents acting every five minutes burn roughly $57 a day against $77 of capital: the position would need to return 75% per day to stand still. The gap between those two modes is about 1000x, and it is the entire product decision. A swarm that thinks occasionally is nearly free. A swarm that trades forever converts its owner's capital into compute.
The arms
Read risk factors and executable, not distinct assets. Ranked by the metric we designed, arm C wins and D looks worst. Ranked by whether it is a portfolio that can actually be placed, the order reverses completely.
| Arm | Distinct assets | Risk factors | Long / short | Executable | Reads as |
|---|---|---|---|---|---|
| ANaive fan-out | 5 / 10 | 2 | 8 / 2 | 8 / 10 | Mode collapse. Same coin ×4. |
| BHand-written niches | 8 / 10 | 4 (+1 fiction) | 7 / 0 real | 7 / 10 | Hedges that can't be placed. |
| CCoordinator, momentum data only | 9 / 10 | 1 | 10 / 0 | 10 / 10 | One bet, ten hats. |
| DCoordinator, real universe | 7 / 7 | 4 | 5 / 2 | 7 / 7 | A portfolio you can fill. |
10 identical agents, identical prompt. The control.
A human wrote ten asset-class mandates. Meant as the ceiling.
A coordinator wrote its own ten mandates from the top-movers feed.
Same coordinator, told exactly which venues can actually fill a trade.
Neither. Ten agents given one instruction produce about three distinct bets — and with a coordinator, about seven. Not a hundred.
The premise half-survives. Fan the instruction out naively and you get mode collapse: ten agents, three asset classes, the same coin picked four times. Put a coordinator in front and give it the list of venues that can actually fill an order, and you get something genuinely worth having — four uncorrelated risk factors, real hedges, everything executable. So the mechanism is real.
The number is not. Asked for ten mandates, the coordinator returned seven and said the rest would be clones. That ceiling isn't a matter of taste or prompt engineering — it's the count of genuinely uncorrelated things our venues can do. A swarm bigger than its venue's factor count is paying full price for copies. At ~7 factors, a hundred agents is fourteen deep on every bet.
So the thing worth building isn't the swarm — it's the coordinator. Agent count is a cost multiplier; the decomposition is where the value lives. And it doesn't need a hundred agents to be useful: every user already has three, which sits comfortably under the ceiling. That's the version we thought we could ship without new wallets, new funding rails, or a single change to how agents work today.
One caution carried out of this: the failure that scared us wasn't the swarm being dumb, it was the swarm being confidently wrong. Told to trade an asset class we don't support, agents wrote a plausible hedge and moved on. A portfolio that reports protection it cannot place is worse than one that admits it has none.
Update: this conclusion did not survive. Every arm above compares swarms to other swarms, which cannot tell you whether a swarm is worth building at all. We ran the missing comparison in Three agents, or one agent thinking harder? — and one agent matched the coordinator exactly, for a quarter of the cost. The coordinator isn't the product either. Read that one next.
What we’re doing about it
Let the coordinator size the swarm
It already does this correctly, for free. Ask for N, get back "only 7 factors exist here." Swarm size should be derived from the venue's factor count, not typed in by the user — an agent past the ceiling is a clone that costs full price and returns nothing new.
Pass the executable universe into every prompt
This single change took an arm from 1 risk factor to 4, and executability from a coin-flip to 7/7. Without it, agents invent hedges in markets that don't exist — a failure that reads as prudence.
Score risk factors, not distinct tickers
A swarm reporting "9/10 distinct assets" while holding one factor is misleading its owner in exactly the way our own metric misled us. Factor concentration is the number that belongs on the dashboard.
Start at three agents, not a hundred
The dispatcher is the product; agent count is a cost multiplier. Every user already has three agents — running the coordinator over those needs no new wallets, no funding split, and sits comfortably under the factor ceiling, so every agent still earns its keep.
"Trade indefinitely until they make money or run out of money"
At $7.69 of capital against roughly $0.48/day of compute, only the second outcome is reachable. This was in the original spec and the numbers removed it.
One token per agent
A hundred agents minting a hundred tokens points a firehose at our own token leaderboard, which is a surface people actually use. If a swarm needs a token, the swarm gets one.
Limits & what we got wrong
- Single run, n≤10 per arm. The gap between arms B and C on distinct assets is inside the noise; the gaps on risk factors and executability are not.
- Our factor classifier miscategorised Arm D's stablecoin depeg-arb trade as micro-cap beta. The factor count of 4 is correct; one label is wrong.
- Arm D's first run was invalid — a bug on our side handed every agent an empty mandate, which silently reproduced the naive control. The published run is the fixed one.
- Agents were asked for a thesis, not to execute. Executability was checked against the live API by rule, not by placing orders.