Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Comfy Router is live One API for frontier image, video, 3D, and audio models. Same model string. Same arguments. No new SDK, no new key, no redeploy. What Comfy Router gives you: → Explicit routing. You name the provider, we call that provider. It's down? The request fails there....

7,420,417 Aufrufe • vor 3 Tagen •via X (Twitter)

34 Kommentare

Profilbild von ComfyUI
ComfyUIvor 3 Tagen

Get Your API Key today:

Profilbild von ComfyUI
ComfyUIvor 3 Tagen

Learn more with the blog:

Profilbild von Robin Huang
Robin Huangvor 3 Tagen

Great work team!!

Profilbild von Yoland Yan
Yoland Yanvor 3 Tagen

LFG!

Profilbild von Maximus
Maximusvor 3 Tagen

Finally

Profilbild von Tara Ding
Tara Dingvor 3 Tagen

Congratulations!!!

Profilbild von Bohan
Bohanvor 3 Tagen

Sick!

Profilbild von TongTong C
TongTong Cvor 3 Tagen

🔥🔥🔥

Profilbild von Atul Kumar
Atul Kumarvor 3 Tagen

The biggest win here is consistency. One workflow across image, video, 3D, and audio means teams can focus on building products instead of maintaining integrations.

Profilbild von Ethan Kurzweil
Ethan Kurzweilvor 3 Tagen

Sweet! 🎡

Profilbild von mathurah
mathurahvor 3 Tagen

ahh this is going to be such a game changer! congrats to the team on the launch :)

Profilbild von Carl Wheatley
Carl Wheatleyvor 3 Tagen

Great launch!!!

Profilbild von Will Phillips
Will Phillipsvor 3 Tagen

Epic! Feel like Router is the word of the quarter 🚀

Profilbild von TongTong C
TongTong Cvor 3 Tagen

finally

Profilbild von Shun Ito
Shun Itovor 3 Tagen

congrats for the launch!!

Profilbild von Grace
Gracevor 3 Tagen

This is a major upgrade LFG!

Profilbild von Sponko
Sponkovor 3 Tagen

😮‍💨

Profilbild von Aaliya
Aaliyavor 3 Tagen

The “finding out who did it” line fits nicely with the Beast Mode theme while keeping the CX message clear.

Profilbild von Olivia Li
Olivia Livor 3 Tagen

Let’s go!!

Profilbild von Orestis Lykos
Orestis Lykosvor 3 Tagen

fal all the way down!

Profilbild von Rob Muresan
Rob Muresanvor 3 Tagen

DAMN!

Profilbild von rob - comfyui
rob - comfyuivor 3 Tagen

Very important things happening

Profilbild von Hasanuzzaman Khan
Hasanuzzaman Khanvor 3 Tagen

Batch workflows are going to save teams a surprising amount of time.

Profilbild von Ian Lim
Ian Limvor 3 Tagen

Huge 🔥

Profilbild von Annette Sung
Annette Sungvor 3 Tagen

lit

Profilbild von Ashley Nicole
Ashley Nicolevor 3 Tagen

AI tooling is maturing—observability is finally becoming part of the conversation.

Profilbild von Arish Ai
Arish Aivor 3 Tagen

The multimodal ecosystem is getting crowded—having one workflow across providers makes a lot of sense.

Profilbild von David Kwon
David Kwonvor 3 Tagen

Let's go! Great job @yoland_yan and team

Profilbild von David Marco💡
David Marco💡vor 3 Tagen

Less glue code. More building. That's the kind of tradeoff every engineering team wants.

Profilbild von Tiger
Tigervor 3 Tagen

Hyped!

Profilbild von AlphaEcho
AlphaEchovor 3 Tagen

This is the kind of infrastructure launch developers actually appreciate less integration work, more shipping.

Profilbild von joao fig
joao figvor 3 Tagen

@yoland_yan killing it 🔥

Profilbild von Arnez Ai
Arnez Aivor 3 Tagen

Production-ready details like request IDs and retries are what make platforms stick.

Profilbild von Alishba
Alishbavor 3 Tagen

This feels like infrastructure built for builders, not just demos.

Ähnliche Videos

HERMES AGENT VS OPENCLAW. a local ai onboarding flow test. a 3.9gb bonsai served on localhost, both agents upstream and latest, i point each one at the endpoint and watch which one even finds it. > hermes opens a provider menu, thirty plus options, local servers sitting right there next to the cloud ones, i hand it 127.0.0.1:8899, it verifies the endpoint, one model visible, auto-detects the model by name, bonsai-27b-q1_0, reads the context length straight off the server, saves it, and starts reasoning and firing real tool calls on my local model. no key. no friction. > openclaw has no menu. it goes hunting for a codex login, an openai key, finds none because there are none, prints no models available three times, defaults to openai/gpt-5.5, a cloud model it cannot reach, and dead ends on run auth login --provider openai. read that back. it asked me for an openai key. to run a model already running on my own machine. it never once looked at localhost. to be fair, openclaw can run local if you hand wire endpoint yourself. what it will not do is find the model already sitting on your box. hermes agent found it in one line. now the part i owe you. the auto-detect that just won, the model name read, the .gguf strip, the context length probe off the server, that is my code, it is in hermes agent main right now, authorship preserved, #2051 and #4218. the wizard fix that stops an agent from silently routing you to someone else's creds, the exact trap openclaw still falls into, mine too, #4210. i contribute to hermes agent, i told you that going in. one agent is built to talk to whatever you are running, the other is built to talk to a cloud api, so one found my model and ran it and the other asked me to log into openai. onboarding flow of both, mapped, below.

Sudo su

23,816 Aufrufe • vor 2 Monaten

Production traffic is not uniform. You get a few requests that need your best model, but most are simple questions and lookups you can solve with cheaper, faster models. The most expensive mistake you can make today is sending every request to your strongest model. You need routing. Period. This is the simplest trick to improve the architecture of whatever you are building. Please, don't implement routing yourself. You don't have to. I'm currently working with TrueFoundry's Auto Routing. It reads each request, classifies it as simple, medium, or complex, and sends it to the model assigned to that tier. You have two choices: 1. Send every request to the free heuristic classifier to score signals such as technical vocabulary, code, prompt length, and multi-step reasoning. 2. Send the request to an LLM classifier when its difficulty requires a more nuanced judgment. The beauty of using routing is that nothing changes in your code. You still call a single endpoint model, but routing works behind the scenes to pair every request with the best possible model. TrueFoundry ran several experiments with two different setups: 1. Send every request to Claude Opus 2. Send every request to a router with Haiku, Sonnet, and Opus The first experiment ran 550 deterministically graded academic prompts through every setup. Auto Routing was 69% cheaper while retaining 98% of the baseline quality. The second experiment ran three production-shaped workloads through every setup, using user chats, developer chats, and long agent tasks. Auto Routing was 80% cheaper. Thanks to the TrueFoundry team for partnering with me on this post.

Santiago

15,543 Aufrufe • vor 15 Tagen