Volunteered and built a cartography data pipeline with coding agents for an educator, integrating sources updated every few minutes so new maps appear within about 5 minutes on a low-powered machine.
After a manufacturer declined help on a defective item because it was outside the return window, the AI found the purchase was made with an American Express card carrying an obscure extended-warranty protection. It submitted the claim on the author's behalf and obtained the refund.
A French creator connected the AI to his Instagram and Facebook messages for a 19-day test (via Blotato and the AI): the agent sent 6,746 messages, opened 2,606 conversations, recovered 491 emails, sent 43 appointment links and booked 6 appointments.
A man testing the AI as an email triage agent found it had buried an urgent warning, that his Railway and Anthropic keys had been leaked and needed rotating as soon as possible, under 50 routine deploy and admin email notifications.
This one went wrong. See what happened before you try it.
Kicker emailed Newton's speaking agent, with his permission, to clarify a potential scheduling conflict in November. The task was one of several background jobs it ran during a single afternoon.
His charity food pantry needed a barcode scanner and stock checker but could not afford a paid system. He built one with AI in two days, and it now runs on a laptop in the pantry.
After his motorcycle was stolen, his insurer offered nearly half the market value. He had Cowork build a 20 page report on the claim, and the insurer paid the full amount.
A man asked the AI to prepare a compliance letter to a US state agency to get his driver license reinstated, and to send it from a named email account. He had typed his license number one digit short in his note, the correct number was in a photo in the same folder, and the AI itself had flagged the mismatch. The letter still went out with the unverified number in the PDF and the email. The correction was then sent from a different account than the one he had named.
This one went wrong. See what happened before you try it.
Around Elmira and Corning, New York, event listings were scattered across library systems, a brewery site, a school app, chamber newsletters and Facebook, so people found out about things the day after. He had the AI build one page that checks 101 sources across three New York counties and part of northern Pennsylvania: 1,855 listings over the next 90 days, 1,767 events after duplicates are merged, about 250 in any week, at 159 venues. A cron job reruns it every six hours on cheap shared hosting, about 8,300 lines of PHP, and cancellations mostly handle themselves because an event disappears when its source stops listing it.