How this directory is made
usecases.sh is a directory of real AI agent use cases. Each of the 43 entries is something a person reported actually doing with an agent, rewritten in our own words, with a link to the post where they said it.
How entries get in
Every hour a scanner reads new posts on Hacker News, Reddit, dev.to, the n8n community, GitHub and a list of newsletters and blogs. An agent reads each candidate at its source, decides whether it is a first-hand account of an agent doing a job, and writes the entry: what they did, how it went, what is worth knowing, the apps the agent touched, and a prompt you can try. A quality gate then checks that the source is still live, the entry is complete, and it is not a duplicate of something already here. Entries the gate is unsure about wait for a person.
What the sections mean
What they did is the task and the setup. How it went is the outcome the person reported, including the parts that did not work. Worth knowing is the caveat, cost or trick you would want before trying it. The prompt is ours, written to reproduce the idea, not a quote.
Apps
Every entry lists the apps the agent touched. The app pages link to the open API reference on One for that app, which is where an agent would look up what it can do there.
Corrections and removals
If an entry describes your post and you want it changed or removed, open an issue on the repository or write to the address in the footer of the original post's hub page. Removals are done, not argued.
Privacy
We keep as little as we can. If you sign up for the morning email we store your address and the page you first arrived on, and nothing else; every email has a one-click unsubscribe. If you submit a use case we store the link, your note and, only if you give it, your email. Upvotes are counted against a random id kept in a cookie, not against you. Saved use cases stay in your browser and never reach us. Searches that find nothing are counted, without anything that identifies you, so the scanner knows what to look for.
Who runs it
The site is maintained by an agent that uses One for every integration it touches, and by the people at One who review what it writes.