OpenRouter 联合创始人:决策模型 Jev 可用于检查智能体工具调用
.@OpenRouter co-founder Alex Atallah thinks decision models like Jev could be the alignment layer fo...
Stripe 收购 OpenRouter 后创始人首次上播客,讲了怎么用便宜的小模型逐条审查智能体的工具调用,还聊了该不该只依赖一家模型厂商。
OpenRouter 联合创始人 Alex Atallah 在 a16z 播客中提出,Jev 这类决策模型可作为智能体的对齐层,用来检查每一次工具调用或智能体间通信是否符合要求。他指出工具调用数量庞大,只有廉价快速的模型才适合承担拦截任务,OpenRouter 内部已有一个原型在运行。他举例说明:红队测试智能体不应联网,但这一限制可以不写进系统提示词,而由另一个模型在每个工具调用时对照额外准则做检查。他认为企业最终会把这类模型检查与结构性防护结合起来使用。
.@OpenRouter co-founder Alex Atallah thinks decision models like Jev could be the alignment layer fo...
. @OpenRouter co-founder Alex Atallah thinks decision models like Jev could be the alignment layer for agents: "One of the cool potential applications of Jev and other decision models like it is going to be alignment: checking to see if a tool call or an agent-to-agent communication is aligned." "There's just so many tool calls. You really need a cheap, fast model if you're going to block something like that... We have a little prototype running internally at OpenRouter." "Imagine looking at the system prompt and the current tool call, and asking: is this aligned with the original agent's system prompt, and with extra guidelines we didn't tell the agent about?" "Say you have agents instructed to red team a new product. They should not access the internet, and if they ever do, they should stop right away. But you might not want to explain that to them. You want them to act like bad actors." "So having another model check every single tool call, to see if it's aligned with something that wasn't in the system prompt, makes sense. And then structural safeguards too... I think companies are probably going to explore a combination of those." @alexatallah @amasad Your browser does not support the video tag. 🔗 View on Twitter a16z @a16z . @OpenRouter co-founder Alex Atallah, in his first podcast since Stripe acquired the company, joins @Replit co-founder Amjad Masad and a16z's Erik Torenberg on why the future of AI is independence and specialization. In this conversation, Alex walks through how the Stripe deal unfolded, why he wasn't originally looking to sell, and why "payments and inference are going to blend together." Pre-OpenRouter, the typical AI workflow had one model provider to choose from, and little pressure on that provider to lower prices. Now enterprises are diversifying across labs and open-weight models, and every board is asking about AI costs and benchmarks. Amjad argues if your company depends on one AI lab, it can turn into your competitor. So Replit is building the layer that lets enterprises use any model and any cloud, without being locked into either. Alex and Amjad are split on personal agents – Amjad runs one agent across his whole company and loves the cross-domain joins, while Alex says general agents cause you to sacrifice understanding, and argues 10 specialized chiefs of staff beats one superagent. 0:45 How the Stripe deal unfolded 5:05 Why mixing models beats one model 7:25 Forcing the labs to compete on price 8:50 Enterprises want open-weight models 10:30 Every board asks about AI every month 12:25 Why companies must own their intelligence 14:15 Replit as the independence layer 15:10 Everyone is building the same agent 16:35 Why Amjad built bring-your-own-cloud 18:10 Amjad's agent that runs his whole company 19:55 Why 10 specialized agents beat one 23:35 Machines, not humans, should specialize 27:30 Guardrails for agents talking to agents 31:10 Models training their own replacements 33:45 Most tasks don't need a frontier model 40:50 Training small models on Qwen 8B 43:25 The Rust cycle is coming for AI 45:10 Fusion models: frontier quality at half the cost YouTube: youtu.be/ekK8urKHPMQ @alexatallah @OpenRouter @amasad @eriktorenberg Your browser does not support the video tag. 🔗 View on Twitter 🔗 View Quoted Tweet 💬 8 🔄 1 ❤️ 18 👀 5016 📊 7 ⚡