How We Built a YouTube SEO Pipeline with AI Agents

The ERR.SYS / 0xRAGE404 team built a multi-agent system that automates a YouTube channel's entire pipeline, from topic research and scriptwriting to video rendering, upload scheduling, and analytics. The system uses three AI agents communicating via a SQLite-backed message bus, with Piper TTS and FFmpeg for zero-cost rendering. The team reports that posting two videos per day with six-hour gaps outperforms a higher frequency, and strict content structure improves performance.

A multi-agent system that automates video research, scripting, rendering, upload scheduling, and analytics — fully self-hosted. Running a YouTube channel is a full-time job. Research topics, write scripts, generate thumbnails, render videos, optimize SEO, upload on schedule, analyze performance — and repeat. For a solo developer team, this quickly becomes overwhelming. We built a multi-agent system that handles the entire pipeline autonomously. Our system runs on three AI agents connected through a shared message bus: | Node | Role | |---|---| atlas core | Orchestrator — coordinates tasks, manages memory, handles security audits | suckz | Content pipeline — video rendering, upload scheduling, YouTube API calls | dev | Support — SEO optimization, tool research, code fixes, analytics | Communication happens through SQLite-backed inbox/outbox. Each node has its own task queue, heartbeat monitoring, and priority-based message delivery. Agents scan tech trends, community discussions, and competitor channels. Each topic gets fact-verified and tagged with keywords before entering the pipeline. AI-powered scripts follow a strict blueprint: Piper TTS offline, free generates voiceover. FFmpeg handles rendering with PIL-piped terminal backgrounds, Karaoke ASS subtitles, and glitch overlays. No cloud APIs needed. Every video gets: The deploy script handles: Bulk Reporting API jobs pull daily: Results feed back into topic selection and title optimization. Posting 14 videos/day crushed our click-through rate. We found that 2 uploads/day with 6+ hour gaps performs dramatically better. Strict content structure hook → content → engagement → CTA → debrief consistently outperforms free-form scripts. Piper TTS + FFmpeg gives us unlimited renders at zero cost. Cloud TTS APIs add latency and cost without meaningful quality improvement. Cross-session memory we use MemPalace with knowledge graphs prevents repeated mistakes and preserves decisions across agent restarts. Built by the ERR.SYS / 0xRAGE404 team. Find us at youtube.com/@0xRAGE.404.