Stripe has reportedly struck a deal worth more than $7bn to acquire OpenRouter, the AI model gateway that gives developers access to hundreds of models through a single interface.
On the surface, this is another major AI acquisition. But if you dig a little deeper, it may also offer a glimpse of how AI agents will be priced in the years ahead – a particularly pertinent point for contact center leaders.
OpenRouter has positioned itself as a layer that lets companies choose between models based on factors such as performance, availability, speed, and cost.
Its CEO, Alex Atallah, previously described the business as “the equivalent of Stripe for AI.”
That comparison now looks especially fitting.
The startup raised a $113m Series B in May at a reported $1.3bn valuation, and claims to provide access to more than 400 models for eight million users globally.
Stripe has not publicly confirmed the acquisition or detailed its plans for OpenRouter. Yet, the reported deal comes as enterprises grapple with the growing problem of AI customer service becoming much harder to cost.
For years, contact center technology has been sold in familiar units. Businesses pay per seat, per agent, per user, or per voice minute, but AI is changing that.
A single automated customer interaction can now involve multiple model calls, retrieval systems, speech-to-text, text-to-speech, workflow tools, integrations, API usage, and escalation to a human agent. The cost of that interaction may also change depending on which AI model is used.
That makes a simple 'AI agent license' increasingly inadequate.
From Per-Seat Pricing to AI Usage
The shift is already underway. Salesforce, for example, has moved Agentforce through several pricing iterations, including conversation-based, action-based, and credit-based options.
The direction of travel seems to suggest that businesses want to pay for AI usage, but they also want far greater visibility into what that usage delivers.
For customer service teams, that should mean looking beyond the cost of a conversation.
A low-cost model might be perfectly suitable for a straightforward order-status query. However, the same approach could fall short when handling a complex insurance claim, a vulnerable customer, or a complaint that risks becoming a legal or reputational problem.
As a result, the model selected for each interaction becomes a CX decision as much as a technical one.
An AI gateway such as OpenRouter gives developers the option to route requests between models. In theory, that could help businesses balance quality, latency, and cost. A service organization could use a cheaper model for common queries, while reserving a more capable one for sensitive or higher-value conversations*
However, there is a risk in treating this purely as a cost-management exercise.
If different models produce different answers, tones, or escalation recommendations, customers may receive inconsistent service depending on how their query is routed.