At its K:BOS customer conference in Boston on September 9, Klaviyo said more than 260 Model Context Protocol tools and more than 490 APIs are now reachable from Claude, ChatGPT, or any agent environment a marketing team already runs. Per the Business Wire release, an outside agent can read a brand’s data, write to it, and put a campaign live without a person opening Klaviyo at all.
The framing is deliberate. Klaviyo isn’t pitching another in-app copilot; it’s conceding that the interface is no longer the product.
“an agent is only as useful as three things; whether it understands a brand’s data, whether it can reach that understanding from wherever it’s running, and whether it can act on it for every individual customer,” said Andrew Bialecki, co-founder and co-chief executive. The company adds that its platform processes more than four billion signals per day, the substrate any external agent would draw from.
Alongside the headless push, Klaviyo previewed SQL inside the Klaviyo Data Platform, translating plain-language questions into queries via Composer and MCP surfaces. Voice is named as a coming channel; forms, flows, and custom objects are on the SQL roadmap.
What’s absent tells its own story. Per The Agile Brand Guide’s September 10 roundup, Klaviyo published no pricing for agent access, no rate limits, and no customer outcome figures. Lapaas Voice noted the governance consequence: for smaller ecommerce operators, approval moves out of the UI and into token permissions, which means somebody has to scope write objects and decide whether sends need human confirmation.
Read against platform-level AI defaults recently pushed by HubSpot and the concentration of AI revenue gains in marketing and sales documented in McKinsey’s 2026 AI survey, the direction is legible. The dashboard operator was the product’s true customer. That customer is being written out.