Agentic Development

Svix launches Poke spec as Standard Webhooks gains major adoption

Svix introduced the Poke specification to support agent-driven event integration, noting that traditional push webhooks are ill-suited for ephemeral environments. The Standard Webhooks spec has been adopted by OpenAI, Anthropic, and Google Gemini.

· 1 source · Webhook standards

Svix, a webhook infrastructure provider, launched a new specification called Poke, described as 'publish once, know everywhere.' The initiative aims to evolve event-driven architecture for the agentic era, enabling agents to easily subscribe to events and trigger asynchronous workflows across services. The spec is inspired by Svix's existing work on polling endpoints and Standard Webhooks, as well as integrations with customers like Agent Mail. Svix has also released plugins for OpenClaw and Hermes to improve local agent consumption of events, allowing agents to poll for missed events rather than relying on push notifications that fail when local machines are offline. The company argues that traditional push webhooks are ill-suited for ephemeral agent environments, such as laptops that go to sleep, and that polling provides a more reliable 'state of the art' for current agent deployments.

The Standard Webhooks specification, co-created by Svix founder Tom Peck-Owen, has been adopted by major AI labs including OpenAI, Anthropic, and Google Gemini. The standard addresses the fragmentation of webhook implementations, which Peck-Owen noted were rarely identical in the wild. Adoption has enabled partners like Kong and Ngrok to implement automatic webhook verification modules. The Model Context Protocol (MCP) is also aligning with the standard, with plans to add webhook support and implement Client Response Confirmation (CRC) to verify client trust. Mercury recently released an Elixir library compatible with the standard. The governance committee for the spec operates in the public on GitHub and follows a 'fast follower' approach, incorporating real-world usage patterns and community needs into the specification roadmap. Peck-Owen argues that standardizing webhooks reduces integration pain and security risks, allowing developers to rely on a sanctioned ecosystem of tools and libraries rather than building custom, potentially insecure signature schemes.