Why AI Agents Still Won't Pay for Anything — Jan Curn, Apify
El artículo aún no está listoTenemos los datos de este vídeo, pero su artículo todavía no se ha escrito. Mientras tanto puedes verlo en YouTube.Abrir en YouTube
Más de este canal
18:56EN
AI Engineer· 27 oct 2026John Feminella: Five Controls for AI Agents, and the $900 Million Bank ErrorJohn Feminella · Two SigmaA payment mistake shows why good intentions and approval prompts are not enough. Feminella describes practical controls for giving agents useful autonomy.
18:12ENAI Engineer· 27 oct 2026Tim Tyler: An Accountability Framework for AI Agents as a Digital WorkforceTim Tyler · GraviteeThe Gravitee speaker applies identity, sponsorship, authority and oversight to agents, drawing on how organizations manage human work.
56:01ENAI Engineer· 26 oct 2026Xander Song on Evaluating Agents with Harbor and PhoenixXander Song · Arize AIArize AI engineer Xander Song explains how Harbor runs realistic agent tasks in isolated sandboxes, and how his team uses Phoenix to compare prompt changes, inspect trajectories, and test a SQL tool.
19:43ENAI Engineer· 26 oct 2026Jack Wotherspoon on Building a Team of Managed AgentsJack Wotherspoon · Google DeepMindGoogle DeepMind’s Jack Wotherspoon introduces Gemini Managed Agents: cloud sandboxes that let teams run coding and research agents with a single API call. He explains how persistent environments, reusable skills, proxy-injected credentials, schedules, and specialized agents fit together.
20:55ENAI Engineer· 26 oct 2026Jesse Hall: Build Voice Agents for Conversations, Not LeaderboardsJesse Hall · LiveKitLiveKit’s Jesse Hall explains how to evaluate voice agents as real-time systems: understand callers, handle interruptions, keep talking while tools run, and measure the delay people actually hear.
18:27ENAI Engineer· 26 oct 2026Daksh Gupta on Building a Better AI Code Review AgentDaksh Gupta · GreptileGreptile co-founder Daksh Gupta explains why a webhook plus a coding agent is not enough for reliable pull-request review—and how targeted prompts, incident data, model inversion, codebase context, browser testing, and task-specific model routing can help.