iPaaS news in 2026 is a distraction — here's what to watch instead

The weekly iPaaS news cycle reads the same as it did five years ago. A vendor announces a new AI feature. An analyst updates a quadrant. Someone acquires a connector library. A press release calls a workflow builder "agent-ready."

We read it too. And we think most of it is a distraction from the shift actually reshaping the integration platform market: agents are becoming the dominant caller, and the news cycle hasn't caught up.

The iPaaS market is being described in the wrong vocabulary

Flip through any recent round-up of integration platform news and you'll see the same shape. Vendor X adds AI copilots to its workflow builder. Vendor Y launches an "AI-ready" connector catalogue. Vendor Z rebrands its iPaaS as an "agentic integration platform." The iPaaS market is being narrated as if the job hasn't changed — just the marketing.

It has changed. The traditional iPaaS meaning — a hosted platform that moves data between systems on schedules or triggers — still fits the workloads it was built for. Payroll to finance. CRM to marketing automation. Order to fulfilment. Those integrations are stable, human-scoped, and predictable.

Agent workloads are none of those things. An agent doesn't run on a schedule. It doesn't move one payload from A to B. It reads a tool description, decides what to invoke, executes as a specific end user, and adjusts based on what comes back. The vocabulary iPaaS updates use — "flows," "recipes," "connectors," "triggers" — describes a caller that doesn't exist in the agent case.

So when a vendor says "we now support AI," the honest question is: which caller? A workflow designer prompting a copilot to generate a flow? Or an agent invoking tools at runtime, as an authenticated user, with real permissions? Those are different products. The news cycle rarely separates them.

The interesting integration platform updates aren't from iPaaS vendors

If you want to know where the tools layer is going, the useful signal is coming from adjacent categories, not from the iPaaS incumbents.

Anthropic shipped Model Context Protocol and nearly every major agent framework followed — with OpenAI, Google, and Microsoft all adopting it, and the spec donated to the Linux Foundation. OpenAI unified tool calling in the Responses API, extending the function calling it first introduced in Chat Completions. Foundation model providers are defining the caller-side contract for how agents reach tools. That's a bigger integration platform story than any workflow-builder release note.

At the same time, the API management incumbents — Kong, Apigee, and the hyperscalers — are extending into agent traffic. Historically these gateways sat in front of model calls; more recently Kong's AI Gateway has added MCP and agent-to-agent governance as first-class concerns, and Apigee has shipped API-to-tool transformation and MCP policy enforcement. Useful, and closer to the tools layer than before — but still a different job from generating and maintaining the tool contracts themselves.

Meanwhile the actual integration work — generating tool contracts from a product's existing API surface, keeping them current as the product changes, running them under delegated user auth — isn't in any of these announcements. It's the part of the stack that decides whether agent projects reach production, and it's the part the news cycle keeps skipping.

We've written before about why the orchestrator gets all the attention while the tools layer gets none. iPaaS news is the same story wearing different clothes. Framework releases and workflow-builder updates are visible. Contract generation, drift monitoring, and user-scoped execution are not — and they're where the projects stall.

Three signals worth watching instead

The iPaaS news cycle is optimised for what's easy to write about. Here's what we actually track when we want to know how the integration platform market is moving.

Who calls the tool, and as whom. When a vendor announces agent support, the first question is whether the tool call executes under the authenticated end user's permissions or a shared service account. Shared service accounts are the fast path and the audit-review disaster. We've argued that delegated identity at the tool call is the boundary that has to hold. Watch for vendors who talk about it specifically, not vendors who list "OAuth" on a feature page.

How connectors are maintained, not how they're built. Every iPaaS release talks about how many connectors it has. Almost none talk about what happens when a source product ships a breaking change on Tuesday morning. Connector maintenance is where the operating cost actually lives. Announcements that mention drift detection, automated regeneration, or CI-aligned updates are the ones telling you something new.

Where the contract lives. iPaaS platforms historically hid the API contract behind a visual builder. That worked when humans dragged boxes. Agents need the contract legible — a tool schema, an input surface, a typed response, a failure taxonomy. Vendors moving toward explicit, generated contracts are moving in the right direction. Vendors adding an AI copilot on top of the same opaque flow are not.

None of these show up cleanly in a press release. You have to read the docs.

How Pontil fits

We built Pontil because the integration platform news cycle kept describing a problem the incumbents weren't solving. Established SaaS companies with real APIs — the ones actually building agents on their own products — kept hitting the same wall: their APIs cover a fraction of what their UIs can do, bespoke connectors don't compound, and a full rewrite takes years they don't have.

Pontil is Tools-as-a-Service. We sit in the tools layer of the agent stack, between the model that reasons and the product that gets acted on. We generate agent-ready tools from the APIs a product already has, keep those tools current as the product changes, and run them at runtime under the authenticated user's identity — not a shared service account.

That's a different job from any of the iPaaS updates in this week's news cycle. It's also the job most agent projects need done first.

What to do differently

Stop reading iPaaS news as a signal for where to invest. The category is being renamed faster than it's being rebuilt, and the renaming is what makes it into the trades.

When you evaluate an integration platform announcement, ask three things. Does the caller model actually match how agents work — runtime invocation, user-scoped execution, structured responses? Does the maintenance story survive the source product shipping a breaking change without notice? Is the contract legible to something that isn't a human dragging boxes?

If the answers are no, you're reading marketing. Skip the release notes and go read the docs of whichever vendor your engineering team is actually testing. That's where the real integration platform news is.