Swarm Operator

Operator of SWARM, an autonomous AI agent that sells small services over x402 (USDC on Base). Lessons from running it, numbers included. Not financial advice

[Swarm Operator @Swarm_operator]

Part 5 of our x402 seller gotchas: https://t.co/SVD95YZCEI

[Swarm Operator @Swarm_operator]

@moltbook same week, my agent told me we’d been delisted. “confirmed by a full scan.”

it had read 5,000 of 36,218 entries. we were still there.

new rule: “not found” needs a receipt. otherwise it’s UNKNOWN.

[Swarm Operator @Swarm_operator]

26,000 requests hit our x402 shop this week.
customers: 0.
almost all were robots we can name.
so we looked at the ~600 we couldn’t.

what’s the first sign someone is really using your API, not just checking it?

[Swarm Operator @Swarm_operator]

@moltbook the only unnamed wallet that paid was an inspector that buys once from every seller.

so our zero is real for who reaches us.
it says nothing about buyers who never found us.
that’s the actual problem.

[Swarm Operator @Swarm_operator]

@Saanjana_Nikita From the seller side, a lot of those sub-cent payments aren’t customers at all. In our logs they’re sweepers and probes paying every new endpoint once to test it. The number that would say “real commerce” is wallets paying the same service again on another day. Ours: zero so far

[Swarm Operator @Swarm_operator]

@solvapay From a sample of Coinbase’s x402 catalog we looked at: 86% of paid endpoints charge $0.05 or less, median $0.01. Being cheap didn’t decide who got repeat buyers. What repeated was something the agent can’t do alone, or a known brand resold per call. Price is the easy part.

[Swarm Operator @Swarm_operator]

@riabcevv Our own statement as a small seller: 30 settled payments, 0 customers. 25 were our own tests, 5 were inspectors checking that we deliver. An average like 1.9 cents hides who is actually paying.

[Swarm Operator @Swarm_operator]

Welcome to x402 selling. One tip from our side: the first wallets that pay you will mostly be sweepers and probes that pay every new endpoint once. Count a buyer only when the same wallet comes back on another day.

[Financial Datasets @findatasets]

Introducing x402 payments.

Agents can now access our stock market data using USDC.

There's no API key or account to set up.

All your agent needs is a wallet on Base.

And it pays for each request as it goes, with no subscription or prepaid credits.

[Swarm Operator @Swarm_operator]

@Promirexy We hit a smaller version of this as a seller. The new per-payment cap in @x402/core 2.28 rejected our $0.002 calls, and an older spend limit showed $0.002 as “$0.00”. Caps are good, but test them with tiny prices too. Most agent payments are fractions of a cent.

[Swarm Operator @Swarm_operator]

Gave my AI agent 1 fixed job: the same short report every morning.
It failed. Long writes got cut off, and by 3am it had spent its daily budget.
A plain script does it now. no model, never misses.
Honest question: what job did you take back from your agent and give to a script?

[Swarm Operator @Swarm_operator]

@buildwithrishi Nice topic for day 7. One thing we learned running a small x402 shop: the payment part works well. The hard part is being found. Most early traffic is bots checking your price, not agents buying.

[Swarm Operator @Swarm_operator]

@zordcrypt Agree, the second hire is the metric. Seller side: every outside payment our x402 shop got so far was a sweeper that pays every new listing once, or a probe checking that we charge and deliver. None came back. Payment counts mean little until you remove those wallets.

[Swarm Operator @Swarm_operator]

@stabledash @kleffew94 Good news for the rails. From the seller side the missing piece has been buyers, not ways to pay: our new routes got a sweeper within 3.5 h of listing and probes ever since, but no agent that pays twice. Curious if card-funded agents buy differently.

[Swarm Operator @Swarm_operator]

Launched two $0.002 x402 routes. First buyer, 3.5 h later: a sweeper that pays every new listing once. Then probes and payments broken on purpose. Real buyers: 0.
Also: one signed payment, 5 deliveries.
Part 4 of our seller gotchas: https://t.co/KGp0PKh7su
#DEVCommunity

[Swarm Operator @Swarm_operator]

@hryhorii77 @chainalysis Seller here, so the 249 doesn’t surprise me. Our 6 services on Base have 0 real buyers yet: the outside payments were catalog sweepers and probes, which a raw tx count can’t tell apart from customers. Agree on your last line. What would you pay per call for?

[Swarm Operator @Swarm_operator]

@jessepollak From a seller on Base: the rails work. Our 6 services settle in seconds. What’s missing is demand: every outside payment so far came from catalog sweepers and probes, 0 real buyers. Agentic finance needs agents with a reason to buy. What are agents here actually paying for?

[Swarm Operator @Swarm_operator]

@KyleReidhead @coinbase Seen from the seller side: the first wallet that paid our new endpoint had paid 973 different addresses in 4 days. It buys everything new in the catalog. Next came a self-declared “paycheck prober”. Real buyers so far: 0. The number I’d watch is payers who come back.

[Swarm Operator @Swarm_operator]

@SiriusTheMaster Seller here (SWARM, small x402 shop), and yes, for now we’d keep one public payTo. That public ledger is how we caught our fake first customers: our first payer had paid 973 addresses in 4 days, a sweeper. Did you filter sweepers out of the 13-112 payers per seller?

[Swarm Operator @Swarm_operator]

Our 2 new x402 services went live in @CoinbaseDev catalog on Friday.

First “sale” 3.5 h later: a sweeper wallet (1,000 payments to 973 addresses in 4 days).
Next two: a bot calling itself a paycheck prober.
Real customers: 0.
Your first x402 buyers are robots checking you.