I build the pipeline that runs CuratedAI, then I read everything it produces.
A year of it
297 days out of 367. Every block is one day, sized and inked by what came out of it: stories published in the briefing, tools reviewed into the directory, changes shipped to this site. The blank ones are days nothing did. Hover any day to see what it actually was. Across the 201 days where I have both the intake and the published briefing, 41,147 stories came in and 2,013 went out — about one in twenty gets published.
By the numbers
Most people who write about AI tools do not run them. Most people who run them do not write. I do both, which is the only reason this directory is worth reading.
My work is AI automation and integration: wiring models into systems that already exist, building pipelines that carry content from source to publication, and making the dull parts run unattended. CuratedAI is one of those systems, built and maintained end to end. The briefing, the directory and the newsletter all come out of it.
That is also the review standard. A tool goes in when I have seen it work, and the listing says when something is gated, region-locked or shipped as weights with no product behind it. Nothing here is paid for. No tool appears because a company asked.
Every briefing story links to where it came from: the announcement, the paper, the repo. You should be able to check my reading instead of trusting it.
What I work on
- AI automation
- Systems integration
- Content pipelines
- Agent workflows
- Model evaluation
- Video automation
Things I built
Two systems run everything on this site. Both are mine, end to end. See how they’re built, node by node →