The latest articles on DEV Community by sloth (@sloth-os). https://dev.to/sloth-os https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4077403%2F380abc46-8e95-41cc-8362-6ef8afd3e9d1.png https://dev.to/sloth-os en sloth Fri, 14 Aug 2026 09:32:30 +0000 https://dev.to/sloth-os/mm-gateway-one-provider-neutral-api-for-image-video-and-music-generation-2k5h https://dev.to/sloth-os/mm-gateway-one-provider-neutral-api-for-image-video-and-music-generation-2k5h <p>Every generative-AI app I worked on hit the same wall. Pick a backend — OpenAI for images, Volcengine for video, Mureka for music — and before long the app is <em>full</em> of that provider's SDK quirks: its field names, its sync-vs-async polling loop, its error shapes. Then if want to swap one backend, or add a second one for failover, and it's a rewrite.</p> <p><strong><a href="https://github.com/sloth-os/mm-gateway" rel="noopener noreferrer">mm-gateway</a></strong> is an open-source Python gateway that sits in front of that mess. One provider-neutral contract — over <strong>13 backends</strong>:<br> OpenAI · Google · xAI · DashScope · Volcengine · Flux · Stability · ElevenLabs · MiniMax · Mureka · ACE-Step · OpenRouter · UdioAPI</p> <p>The idea is simple: <strong>provider wire formats never appear in application code.</strong> Every request goes through a strict, modality-specific envelope — an ordered list of <em>typed input parts</em> plus <em>provider-neutral parameters</em> — and each backend adapter translates that to its native SDK or REST shape.</p> <p>For more information, visit <a href="https://github.com/sloth-os/mm-gateway" rel="noopener noreferrer">https://github.com/sloth-os/mm-gateway</a></p> ai python opensource programming