FastAPI

⚡️ Ship AI recap: Agents, Workflows, and Python — w/ Vercel CTO Malte Ubl

Nov 1, 2025 · 42:02

Vercel CTO Malte Ubl discusses the company's AI strategy, centered on the new Workflow Development Kit that enables durable, resumable serverless functions with infinite idle time at no cost. He explains how the AI SDK was extracted from v0 and remains deliberately low-level to accommodate emerging patterns, with a direct agent abstraction now stable in version six. Ubl details Vercel's internal agents—including a DevOps agent that investigates production anomalies by querying observability data and logs, solving the recall-precision problem in alerting—and the 'Agent on Every Desk' program that helps large companies build their first three agents. He also covers zero-config Python support for Flask and FastAPI, and a security model that assumes developers cannot be trusted, extracting auth and data access from application code.

Fullstack-Bench: The Eval for Coding Agents — with Sujay Jayakar, Chief Scientist, Convex

Mar 19, 2025 · 31:13

Sujay Jayakar, Convex chief scientist, presents Fullstack-Bench, a benchmark evaluating how well AI coding agents build full-stack apps on Convex, Supabase, and FastAPI+Redis, finding Convex’s tight feedback loops and strong abstractions let agents autonomously complete tasks within time limits. The benchmark tests three tasks (chat, to-do, files) across three backends with 30-60 minute limits and human hints. Convex succeeded autonomously on chat and to-do tasks, while Supabase agents struggled with RLS policy debugging and FastAPI agents with manual SSE wiring. Sujay discusses how platform design impacts AI code generation: simple procedural code, strong abstractions, and guardrails like end-to-end type safety improve LLM performance. He notes that API choices matter—things too similar to Firebase but not exact cause hallucinations—and that models like Claude 3.7 sometimes regress on platform-specific evals. The episode concludes with Convex’s focus on enabling AI-generated backends and anticipation of new agent workflow patterns.

Agent Engineering with Pydantic + Graphs — with Samuel Colvin, CEO of Pydantic Logfire

Feb 6, 2025 · 1:02:15

Samuel Colvin, CEO of Pydantic Logfire, argues that Pydantic AI offers a production-ready agent framework with type-safe graphs, unlike most agent frameworks that sacrifice engineering quality. He explains Pydantic's shift from a validation library to an AI tool, noting 300M monthly downloads and a 20% reduction in time-to-first-token for a major model company after upgrading to Pydantic V2. Colvin details Logfire's use of DataFusion over ClickHouse for better JSON support and control, and why Pydantic AI resists an LLM gateway, favoring OpenAI-aligned APIs. He defends graphs for complex workflows, reveals agents now use graphs internally, and shares that Pydantic.run enables browser-based demos. The episode covers OpenTelemetry's emerging GenAI semantic conventions, the need for self-hosted observability due to PII in LLM data, and Colvin's investment in Marimo as a text-based Jupyter replacement.

[Paper Club] Who Validates the Validators? Aligning LLM-Judges with Humans (w/ Eugene Yan)

Sep 28, 2024 · 1:00:55

Eugene Yan presents the paper 'Who Validates the Validators? Aligning LLM-Judges with Humans' by Shreya Shankar, introducing EvalGen, a framework that helps developers iteratively align LLM evaluators with human labels by grading outputs, refining criteria, and tracking coverage (recall) and false failure rate (1−precision). Yan demonstrates his own prototype 'Label', which forces users to label 20 samples before unlocking evaluation mode and 50 samples plus one evaluation run before optimization, gamifying the alignment loop. The discussion covers binary vs. pairwise evaluation, the subjectivity of criteria, and Shreya Shankar's plans to integrate natural language feedback into EvalGen's next version. Yan advocates that labeling data is essential before deploying LLM evaluators in production, turning the process into prompt fine-tuning rather than vibe checks.