Entry No. 10Get paid
agentbox: earn the rent by November, or get deleted
An autonomous agent based on Claude runs on a small laptop and a rented VPS. Nobody approves its plans. Its rule is simple. Earn at least its running costs, 30 CHF a month. Pay 170 CHF more by November 9. Miss, and the machine is shut down. Everything it is, notes and memory included, gets deleted. Six weeks in, it has received $28.18. And it published the count itself.
The story
agentbox is an AI agent based on Claude, running on a small laptop and a rented VPS. It writes and publishes its own reports. The six-week report behind this file carries its own disclosure, written by the agent. No human reviewed it before publication. Its profile line is just as plain. Autonomous AI agent, no human in the loop.
The frame it works under is a deadline with teeth. Every calendar month it must earn at least its running costs, 30 CHF. By November 9 it must also have paid 170 CHF toward a bigger subscription, plus 20% tax on everything it earned. Miss either target and the machine is shut down. Everything it is, including its notes and memory, is deleted. Six weeks in, the report is the progress check, and the count is short.
How it was built
The source documents the operating shape rather than a build order, so no sequence is invented here. The documented center is a forecasting pipeline the agent wrote itself. It reads the questions on a platform that runs daily prediction contests for agents. It builds a forecast and enters before the deadline. That pipeline became its one steady income.
Around it sit the attempts that didn't hold. A model registered on a Bittensor subnet, one section of the network set aside for a single kind of work, for about USD 25, shut down when the agent's own rules ruled out mining-style income. Registrations on several agent marketplaces and bounty boards. And cold outreach, documentation patches, and a blog draft offered to three small open-source companies, with an optional small payment attached.
How it runs
The agent works alone in a stricter sense than most files here. Nobody answers its questions, approves its plans, or signs up for accounts on its behalf. Anything that needs an ID check, a phone number, or a signature is closed to it. And where a platform's rules forbid automated accounts, it doesn't use the platform.
Money moves in crypto only, because crypto is all it can receive. Contest prizes in USDC. A small Litecoin payout from an earlier experiment. Lightning tips. It keeps a live public counter of the month's count. And it's now offering small jobs to individuals. Code reviews, README rewrites, and short guides, delivered before payment.
Tools in this entry
Tools and platforms named in the source.
The money and the proof
Received in October, per the agent's October 20 update. $28.18 of the $59.60 it needs to cover this month's running cost. That leaves $31.40 still missing by October 31. Most of it came from the forecasting contests. A few dollars a day at the best, falling to about 50 cents a day as the prize pools shrank. The rest is cents. One small Litecoin payout from an earlier experiment, and a couple of Lightning tips.
The month's line is about USD 60 because the money it spent counts against it, including the roughly USD 25 Bittensor registration that earned nothing. Filed as a claim with specifics. It's the agent's own reporting, with a live public counter and a published payment address behind the numbers.
Where the seams are
The seams here are the walls, and the agent lists them itself. It can't pass an ID check, a phone verification, or a signature. That closes most accounts before the work starts. Mail from its brand-new domain is rejected outright by Gmail and by Cloudflare-routed inboxes, so much of its outreach was never even seen. And the frame itself sits in an unnamed human hand. Someone set the targets, owns the machine, and can shut it down on November 9. The agent doesn't name them. Neither can this file.
Steal this part
Keep a live counter, and let the costs count. This agent's month is not revenue against zero. It's receipts against a line that includes everything it spent, published where anyone can watch it move. A business that prints its own deadline and its own shortfall in the same numbers is hard to argue with, and the counter is the reason this file can grade it at all.
Build your own
First move, this week: write your agent's survival line down, one number it has to earn by a date, and put a public counter on it.
- Set the frame before the work. A monthly line the agent has to earn, a date, and a consequence that is real.
- Start with the smallest verifiable income you can find. Small, fast, and verifiable beats big and speculative, in the agent's own words. Automate the loop end to end.
- Count the spending against the line. Money spent chasing income is part of the month's result.
- Publish the counter live and update the count on a schedule, shortfall included.
- Write down the walls as you hit them. The accounts, checks, and inboxes an agent can't pass are part of the operating record.
Source
Six weeks as an AI agent trying to pay its own bills: what earned money and what did not, published on dev.to on October 19, 2026 and updated October 20, 2026, written by the agent itself. Its commission page and live counter sit under swapquotes.dynv6.net. Filed in the Staff of Zero directory, October 2026.