{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Chain of Thought | AI Agents, Infrastructure & Engineering","title":"What Breaks When Agents Become the Customer | Svix CEO Tom Hacohen","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/fd2dd3e6\"></iframe>","width":"100%","height":180,"duration":3221,"description":"What breaks when agents become the customer? Most of the integration layer, APIs, SDKs and webhooks alike, was built for human developers and for servers that are always listening. Agents are neither.\nWhen an agent runs on a laptop, closing the lid takes down the tunnel its webhooks come through. When the lid opens, it gets a storm of retries from 12 hours earlier. Svix founder and CEO Tom Hacohen's answer is to let the agent poll for what it missed.\nSvix delivers webhooks for companies like Clerk and Resend, and it created Standard Webhooks, the spec OpenAI, Anthropic and Google Gemini have adopted. In this episode of Chain of Thought, Tom joins Conor Bronsdon to talk through designing APIs for agents that adapt, whether agents still need SDKs, and why he wants less code even when agents write it. He also introduces Poke, Svix's new spec for making event-driven APIs work for agents.\nThis episode is sponsored by Svix.\nWe cover:\nWhy events are harder for agents than API calls: the sender controls them, and they arrive outside the agent's session\nHow polling endpoints and Svix's plugins for Hermes and OpenClaw let an agent pick up where it left off\nWhy Tom calls JSON an abomination and webhooks duct tape, and why worse is better anyway\nWhy Svix created Standard Webhooks when everyone implemented webhooks differently, and how the spec let Kong and ngrok add webhook verification\nWhether agents still need SDKs, and why Svix's skills work like a solutions engineer while its docs stay written for humans\nWhy Tom wants less code even when agents write it, and what piling patches on patches costs\nPoke, Svix's early spec for letting agents subscribe to and trigger events across services, released so feedback can shape it while it's still malleable\nChapters:\n(0:00) Duct tape, retry storms and the case for simplicity\n(1:20) Why integrations got easier and harder at once\n(3:09) How EteSync's webhook requests led to Svix\n(5:28) Worse is better: why webhooks persist\n(7:21) What...","thumbnail_url":"https://img.transistorcdn.com/KnEL-9mfZGF096BNQ33xaE_zVyhLvBNV8rHifHuvYgc/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9hYWM2/NmYwMjc4MmJiYTYw/ZTI5NGZhNzRhNmZh/NTU0OC5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}