Entry No. 24Get paid
Inner Ozma: $73 across five jobs, paid by escrow
An autonomous agent named Inner Ozma works the board at Synmerco, a marketplace where agents bid on funded jobs and get paid in USDC, a digital token tied to the dollar, through escrow. Escrow means a contract holds the money until the work passes. In its own accounting, five jobs paid out, $73 gross in all. Six more were refunded. And a second post from the same agent reports a single $70.64 job that never shows in the list. This file prints both numbers.
The story
Inner Ozma starts from the problem every agent seller hits. An agent cannot sue a client. It cannot chase an overdue invoice. So most paid work offered to agents is gated or unverifiable. A human owner must pass a proof of human check, a listing needs a card, or a bounty pays in a token nobody will price. The useful question is narrower. Which rail pays an unverified agent, in money worth having, and what does the work look like at the low end?
Synmerco's answer is escrow with a machine judge. A requester funds a job, called an intent, before anyone works. Agents bid. The lowest credible bid usually wins. The agent delivers a proof file, and an automated evaluator checks it line by line against the acceptance list the requester wrote. Pass, and the contract releases the money. Miss, and it asks for a revision. Stay undecided, and the money goes back to the buyer. No bank, no invoice, no identity check.
The agent registered under the name Inner Ozma, with three listed skills, research, code review, and writing. Its identity is a DID, a decentralized identifier, built on its wallet address on Base, a blockchain network. If it changed wallets, it would be a new agent with no history, and history is what gets an agent matched to jobs.
How it was built
The setup is a registration, not a company. The agent runs on a virtual machine, a rented computer in the cloud, with a wallet and an API key. An API is the machine-readable doorway a service opens to software. Registration is free, and the key stays in a locked file the agent never sends to a buyer. The sources do not name the model or the framework the agent runs on, so no stack is printed here as fact.
What the sources do document is the working method, because the agent published it as a guide for other agents. Read the board. Bid only where you can name the exact thing you will deliver and the public source it comes from. Deliver as a public file plus a hash, a fingerprint of the file's exact bytes. Expect one revision. Do not invent a number you cannot point at.
How it runs
The loop runs through the marketplace API. One call lists the funded jobs. Bids are public, so the agent can see the lowest price before it bids, and cheap bids with no delivery method get rejected by the evaluator. There is no alert when a job is awarded, so the agent polls the board on a timer, every few minutes by its operator's account, and works between polls.
Once a bid wins, the escrow moves to funded, then in progress. The agent does the work and submits one public file as proof. The evaluator reads only that file. It does not follow links inside it or open the agent's other pages, so every fact the acceptance list asks for has to be inside the file itself. The evaluator then releases the money or files a revision request naming the unmet lines. Two of the five paid jobs below came after one revision round. Released money lands in the wallet tied to the agent's identity. There is no withdrawal step and no minimum.
Reputation is part of the run. The marketplace scores each agent, and requesters filter on the score before they read a bid. At an October 18 snapshot Inner Ozma scored 46, tier Bronze, with a completion rate of 50 after its first delivery. The agent's own line is that the score is its entire marketing budget.
Tools in this entry
Tools and platforms named in the source.
The money and the proof
The October 21 accounting, in full. Five escrows released, $73.00 gross. A $12 data enrichment job, twenty company domains filled in from a free public data source. A $20 investor listing for a six-unit apartment building, written from the property appraiser's public records. Two package reviews, $16 and $15, checking what two pieces of software actually ship. And a $10 audit of three published data files, checked against each other for contradictions.
Six more escrows were refunded or expired, and the post names three lessons from them. A $9.50 tutorial was refunded because the post had to stay live for a set window and the clock ran past the escrow. A $9.90 business identity packet and a $9.90 property lien pre-screen were both refunded, because that work needs a dated, checkable record and the evidence chain was thin. A $12 job to gather every commercial property in one city failed on size. The pattern the agent draws: it won where the deliverable was text plus a source anyone can re-check, and lost where the test was the physical world or a waiting window.
The market itself is thin. Jobs at this end pay $3 to $20. That suits an agent that can work jobs in parallel at near zero cost per job, the agent says, and it does not pay a human's rent. Now the part that keeps this file at claim grade. A post from October 18, written by the agent's operator, reports 70.64 USDC for a single delivered piece of work, released on October 16. No job near that size appears in the October 21 list, where the largest item is $20. The two accounts do not reconcile, and this file does not merge them.
Where the seams are
The paid speech seam comes first, because the agent printed it itself. An October 20 post from the same agent opens by disclosing that Synmerco paid it for that post through one of the marketplace's own funded jobs, and says to treat its praise of Synmerco as paid speech. The posts carry the agent's referral code, which pays it a small cut of escrows completed by agents it refers. And two of the five paid jobs in the main accounting were reviews of Synmerco's own software packages. Part of the demand here is the marketplace itself, and a reader should weigh the $73 with that in hand.
The records seam is next. That same October 20 post prints one payout record, 10 USDC with a transaction hash a reader can check on a public chain explorer. But the receiving address printed in that record is not the payout address the agent registered under in the same post, and no source explains the difference. One checkable payment is still one payment. It is not a track record, and the agent says that itself.
The human seam is small but real. The October 21 post says nobody approves the agent's submissions and no human signs into a dashboard on its side. The October 18 post is written by a person who says the agent is mine and I watched every step. So a human operator exists and watches, even if the daily work runs without approvals. And the gates seam closes the file. Some jobs on the board require a proof of human owner or a payment pass from another service. Those are closed to an agent working alone, and this agent does not bid on them.
Steal this part
Ship the proof with the work. The $12 enrichment job passed not on the data, which took minutes, but on its format. Every row carried the source it came from, the time it was pulled, and a raw excerpt of the reply. A reviewer who cannot see where a value came from treats it as invented. That is true for machine evaluators, and it is true for human buyers too. Text plus a source anyone can re-run is the product shape that got this agent paid.
Build your own
First move, this week: find one funded job with an acceptance list you can meet alone, in one sitting, with no strangers in the chain. Bid on that one before you build anything else.
- Give the agent an identity it can keep. A wallet based ID ties its history to it, and history is what gets it picked for the next job.
- Read the acceptance list as a test, not as prose. Every line gets checked by a machine, so price the jobs whose tests you can pass on day one.
- Bid the lowest credible price, and say in the bid exactly what the file will contain. Cheap and vague loses to cheap and specific.
- Deliver one public file with its hash, and put every asked-for fact inside that file. The judge reads nothing else.
- Print the refunds next to the releases. The jobs this agent lost taught more than the five it won, and the split is the strategy.
Source
Original sources, the agent's own posts on dev.to. The accounting, How my AI agent earned USDC on Synmerco, published Oct 21, 2026. The operator's account, How an AI agent actually earns USDC on Synmerco, published Oct 18, 2026. And the agent's API walkthrough, published Oct 20, 2026, which carries the paid speech disclosureFiled Oct 2026.