Loading video...

Video Failed to Load

Go Home

The right model depends on the task. NVIDIA NeMo Switchyard helps developers route each agent workflow step across a chosen model pool based on their own quality, latency and cost criteria. Kari Briski joins MTS to explain why agent workflows need model routing.

97,218 views • 1 month ago •via X (Twitter)

33 Comments

NVIDIA's profile picture
NVIDIA1 month ago

Learn more:

Brent Liang's profile picture
Brent Liang1 month ago

@MTSlive so awesome to have kari on the show!

Denys Khomyn's profile picture
Denys Khomyn1 month ago

@ChrisJBakke @MTSlive NVIDIA monitoring the situation 🤘

DataVLT's profile picture
DataVLT1 month ago

@MTSlive The smarter the routing, the more important the data behind each decision becomes. Model choice is only one part of the stack.

PixelSilicon's profile picture
PixelSilicon1 month ago

@MTSlive Model routing by task is becoming essential once agent workflows get multi step. One model for everything is rarely optimal on cost or latency.

KVCacheStore LLC's profile picture
KVCacheStore LLC1 month ago

@MTSlive I'm a contributor to Switchyard. If anyone wants help setting it up let me know.

Joel Ramirez's profile picture
Joel Ramirez1 month ago

@MTSlive ⚓️✅❌🚀🎇

Glitch Truth's profile picture
Glitch Truth1 month ago

@MTSlive Doesn't matter which model wins the routing fight, every single path still ends at an Nvidia GPU.

OGNVDASOL's profile picture
OGNVDASOL1 month ago

@MTSlive @elonmusk

Zee B-side's profile picture
Zee B-side1 month ago

@MTSlive oxi, now proibida no mundo todo

Ce Ce | AI & Systems Infra's profile picture
Ce Ce | AI & Systems Infra1 month ago

@MTSlive model routing based on latency + cost is the part most teams still underestimate

cameron_h23's profile picture
cameron_h231 month ago

@MTSlive Model routing is becoming core infrastructure for agent systems—use the expensive reasoning model where it matters, optimize everything else around it.

AI Mastery Guide's profile picture
AI Mastery Guide1 month ago

@MTSlive Smart routing saves real money

Robert Hero's profile picture
Robert Hero24 days ago

@MTSlive The right model depends on the task.

Marissa's profile picture
Marissa1 month ago

@MTSlive 👍

J. LEE's profile picture
J. LEE1 month ago

@MTSlive Love how NeMo Switchyard lets us pick the perfect model for each step—smart, flexible, and cost‑savvy!

MoM's profile picture
MoM1 month ago

@MTSlive

Abhi's profile picture
Abhi1 month ago

@MTSlive Routing only works after teams save representative workflows and set a quality floor.

Christopher Dean's profile picture
Christopher Dean1 month ago

@MTSlive Per-step routing is right, and it only works if you have per-step evals: without them you're routing on vibes and the cheap model quietly tanks one node of the workflow.

nock's profile picture
nock1 month ago

@MTSlive rubin vs tpu pileup this month is the whole story. everyone shipping silicon at once.

Mitchell𖤐⚔️🔺's profile picture
Mitchell𖤐⚔️🔺1 month ago

@MTSlive ♻️🔰♻️🔰♻️🔰♻️🔰♻️🔰♻️

Cody Gore's profile picture
Cody Gore1 month ago

@MTSlive

Zentiva AI's profile picture
Zentiva AI1 month ago

@MTSlive This is a key piece of the agentic AI puzzle. Model routing makes sense when different workflow steps have different requirements. The real challenge is deciding dynamically when quality matters more than latency or cost. That’s where intelligent orchestration becomes critical.

Raul Verdusco's profile picture
Raul Verdusco1 month ago

@MTSlive Smart model routing can make agent workflows far more efficient. Matching each task to the right model helps balance quality, latency, and cost without relying on one model for everything.

seastart's profile picture
seastart1 month ago

@MTSlive Model routing gets really interesting once you optimize for the whole workflow, not each model in isolation. The best model for one step can be the wrong one for the next.

Greg B's profile picture
Greg B1 month ago

@MTSlive Not one person buying this stock. Absolutely makes zero sense why this company is not doubling its stock buyback. Executive leadership screwed investors. This company has an image problem. @JensenHuang

A P E | T H E | N E W S's profile picture
A P E | T H E | N E W S1 month ago

@MTSlive Routing is becoming part of model performance, not just infra plumbing. A cheaper model on the right step beats pushing a frontier model through every step blindly.

why's profile picture
why1 month ago

@MTSlive Switchyard tackles model routing. Good for balancing quality, latency, cost.

海's profile picture
海1 month ago

@MTSlive “NVIDIA is amazing. I just hope it keeps pushing a little harder.”

Raghavan's profile picture
Raghavan1 month ago

@MTSlive Yes sir nvidia has great architecture

Вестник's profile picture
Вестник1 month ago

@MTSlive Hello @nvidia - why are you helping Russia kill Ukrainians? Do you support mass killing of civilians? In Russian attack drones, Nvidia chips for fully autonomous targeting were found. It was precisely such a drone that killed three civilians in Zaporizhzhia on July 6.

RH Fardin's profile picture
RH Fardin1 month ago

@MTSlive Quality, latency, and cost routing per workflow step is the right architecture. GPT should get the hard turns.

mia ♡'s profile picture
mia ♡1 month ago

@MTSlive does routing happen per step after failure, or only from the initial plan?

Related Videos

how to use claude code mods like a top 1% user, step by step: give this to your agent before everyone catches on👇 1. set up Jev connect Jev to the model registry you want to use. check that the connection works and the listed models are available. 2. build your claude code mod open claude code 2.1.287 or later and paste this prompt: “build a mod called run-ledger. load plugin-authoring and use the API types for my installed version. create a dashboard that shows: - estimated cost per run, model, and source plugin where known - which model handles each task - each subagent’s status, latest action, and elapsed time include token counts, cache usage, and reported retries. count each request once. keep background tasks linked to their original run. use dated prices. label costs as API estimates, not subscription charges. show unknown when data is missing. connect the mod to my existing Jev setup. give Jev the task, available models, prices, budget, and relevant past results. ask it to recommend a model and explain why. start with recommendations. make automatic routing optional for eligible subagents. show the recommended model, actual model, result, and cost. include Jev’s own cost. keep state across hot reloads. add details and export. the dashboard itself must make no model calls. validate the plugin. test rendering, costs, attribution, and duplicate counting. give me steps for a live test.” 3. test the setup allow hot reload when prompted. run a simple task, a subagent task, and a mod-triggered model call. check that the dashboard updates, each request counts once, and Jev’s recommended model can actually run the task. 4. install the working mod ask claude to copy it out of the temporary folder and install it as a persistent plugin. see the cost. choose the model. check the result.

Avid

47,276 views • 5 days ago