Rethinking APIs for agentic operations

 

 

To embed our video on your website copy and paste the code below:

<iframe src="https://www.youtube.com/embed/IOeaHSew2cg?modestbranding=1&rel=0" width="970" height="546" frameborder="0" scrolling="auto" allowfullscreen></iframe>
Guy Daniels, TelecomTV (00:29):
Well, welcome back everyone. Two more sessions to go for this year's DSP Leaders World Forum. So welcome back into the room and to our audience who's watching us online. Hoping you've been entertained by Tony's Extra Shot. Two more sessions and there is a bonus extra shot at the very end of the day — don't miss that one. So we are going to start off the afternoon sessions with our first panel, which is Rethinking APIs for Agentic Operations. Now, despite many global telco initiatives, commercial API traction remains somewhat limited. Telcos have been a bit fragmented with perhaps overly complex APIs that lack market demand, while monetisation has remained by and large a bit elusive. Now, telcos are addressing this. They are looking to fix it. They are moving on this. But we want to know how telcos will finally execute on a network API opportunity and build valuable platform businesses when developer interest is focused an awful lot on MCP and agentic operations.

(01:39):
So first of all, let's meet our panellists. I'm going to ask them to introduce themselves briefly, starting on my far left.

Diego Lopez, Telefónica (01:46):
Well, I'm Diego Lopez. I work for Telefónica and recently, as I said yesterday, have been appointed as responsible for data and enablers in our innovation branch.

Guy Daniels, TelecomTV (01:56):
Thanks, Diego.

Raman Mistry, GSMA (01:57):
Hi, I'm Raman Mistry. I'm the Channel Partner Lead for GSMA's Open Gateway.

Guy Daniels, TelecomTV (02:03):
Thanks, Raman. David.

David Boswarthick, ETSI (02:04):
Hello. My name is David Boswarthick. I am Director of Strategy and Innovation for ETSI, the European Telecommunications Standards Institute.

Nathan Rader, Deutsche Telekom (02:13):
And I'm Nathan Rader. I'm working for the DT Group, responsible for some of our network API products and also a board member for the CAMARA project.

Guy Daniels, TelecomTV (02:25):
Great. Good to have you all on this session. And Nathan has kindly agreed to be our DSP co-host. So before we begin our panel discussion, I'm going to ask Nathan if he'd like to go to the podium and give our DSP Leaders address.

Nathan Rader, Deutsche Telekom (02:43):
Yeah. So I guess I want to start by maybe throwing some water on the AI fire to begin with, even though this is about AI. I think that we need to focus the industry currently and not chase AI in the network API space just because it's the latest buzzword, the next shiny object out there. We need to think strategically about where we use AI, how we enable it for the various partners so that we can actually move forward. As was said in the intro, we're just starting to get to that point where we've got enough of an ecosystem built out. Monetisation is starting to come in early. And I think that if we all of a sudden jump away from focusing on monetising the APIs and go, "Oh, now we need to make everything agentic and AI enabled," we're going to lose that ability. So if we focus and look at the network as a three-layer stack, the API ecosystem — there are plays in all of those that we can use AI for, but we need to really make sure we're focusing on the right bit.

(03:49):
So if we look at the very bottom layer, that's the individual telco. Each telco, each network — of course there's plenty of opportunity to use AI there. We can use whatever tools are available to help us develop our API use, nothing wrong with that. We take the next step up and we look at the aggregation layer. That's a middleware — it's really there to help enable the ecosystem. It really shouldn't have a lot of AI focus. Again, use AI to build out the software, but leave it there. The real place we need to focus on for the end user, the end developers, where we use AI is on that third layer — the upper layer — which is the exposure layer towards the market, the go-to-market channels. That's where people need to consume it.

(04:38):
That's where everybody's going to want to start looking into agentic AI and things like that. But what that means is that we as telcos maybe don't need to put so much focus down in our bottom layer on making things agentic AI-enabled to start with. We should start by making sure the APIs are there. In some of the previous sessions we heard this — everybody's saying, "Get those standard APIs out there, make them available in every market." That's where we as telcos need to continue to focus. Get that out there and then let the channels build that agentic experience and get it out into the market. Now, of course, there are some telcos that are looking to become the channel and go to market themselves, and by all means — but don't get distracted by chasing agentic AI and MCP just because that's the hot topic of the day.

(05:34):
So that's a little bit of water on the AI fire for the moment.

Guy Daniels, TelecomTV (05:39):
Thanks indeed. And I think it's good to put a little bit of water on this at this stage — very interesting. It's hopefully going to tie in with our conversation here. Interesting three-layer stack. That's something I'd like to go straight to — the exposure layer, the go-to-market layer at the top. Perhaps we can focus on that first. I'd like to get an idea of which network capabilities and go-to-market strategies are going to enable a telco API business to compete with the cloud and CPaaS providers if they so desire. Raman, you're doing a lot with Open Gateway — can you give us an update?

Raman Mistry, GSMA (06:28):
Sure. First, I'd just like to reiterate what Nathan said about let's monetise what we have today. We know that agentic AI and MCP are coming down the line. From a GSMA perspective, from Open Gateway — which is the supply side of the equation — we also have GSMA Fusion, which is the demand side, where we're working with enterprises. And what we're seeing is APIs around solutions on trust and security are the ones that are really winning today. Around two-thirds of the deployments we see around Open Gateway are revolving around those. And then what's coming down the line are areas such as quality of service, QoD, device and location-specific APIs. So from a telco perspective, it's not about trying to outcompete the hyperscalers — it's about looking at where the value is from the network.

(07:41):
And the value is, as has been said over the last couple of days, the goldmine of data and the trust signals that network operators have, and using that to monetise solutions. From a go-to-market perspective, my area is working with channel partners, and that's an essential part of the equation — they enable that route to market. And it's not about selling APIs — it's about selling solutions. Maybe a combination of a number of APIs that actually build towards an outcome and a solution. So I think that's another focus area we should look at from the ecosystem perspective.

Guy Daniels, TelecomTV (08:23):
Great. Thanks. Diego.

Diego Lopez, Telefónica (08:25):
The point is — competing in which terms? Because the product that telcos can offer is not the product that... I mean, we're not trying to compete with the hyperscalers. We're not trying to provide big data centres in which you can run your workloads. What we can provide is, as Raman said, access to information that is associated with the network, the pervasiveness of the network, and the association of users with the network — location, security. Related to this, during one of the sessions at lunch I was talking about an experiment we made recently. We were showing it at the Red Hat Summit last week — how we were using the CAMARA APIs for attesting the position of infrastructure or of workloads. This is something that is very difficult to offer by any other means.

(09:34):
And this is not about competing — it's about complementing and showing that using those APIs and those solutions, things are easier, faster, more reliable. As long as we manage to do that, we are done, I would say.

Guy Daniels, TelecomTV (09:55):
Nathan, I framed this as competing with, but maybe as Diego says, complementing is equally valuable.

Nathan Rader, Deutsche Telekom (10:03):
It's a little of both, I think. In the end, we ultimately own the portion of the network and the SIM cards that we have. So when we sell an API, no matter which channel it goes through, we will still be the ones terminating on our footprint — so we always benefit, even without competing. But at the same time, a lot of us as telcos do have an enterprise sales team that would like to go out there and sell APIs alongside SIM cards, phones, and connectivity. And in that sense, yes, we may compete with some CPaaS players. But in order to actually compete, we need aggregation. We need to be able to go in and say, "We've got entire market coverage or global coverage" — which means we're going to have to partner with either a CPaaS provider, Aduna, or somebody that will allow us to get that.

(11:02):
So it's a little bit of co-opetition, more than anything.

Guy Daniels, TelecomTV (11:07):
David, do we have the right environment for this? Are we working on improving the environment for this?

David Boswarthick, ETSI (11:11):
Yeah. From a standards perspective, we see all of the players coming to the table and trying to progress on this. So complementing and competing is the right approach. The operators we observe are trying to get the most value out of their networks by exposing their APIs. What we're seeing now with the CAMARA initiative is focus on essential APIs. And that comes back to your question — fraud detection, SIM swap, number verify, location, network capabilities. In ETSI ISG MEC, we've been working on the capability at the edge, how that can be exposed to the user so they can then further use it. In 3GPP there's work on CAPIF and NEF looking at exposing the capabilities of the network. And the work happening in GSMA is actually saying, "Okay, these are the APIs, these are the formats." So I think we've got this intelligent, safe and secure platform.

(12:05):
If we can agree on a limited set of APIs, get the format right, and expose it to the banking sector — where they don't want to interwork with different APIs for telecoms, they just want one API — then trial and test by doing. And when that API works, let's try another one, then another one. But focus where value can be made quickly.

Raman Mistry, GSMA (12:25):
Yeah. I think there's also an important inflection point. Open Gateway has been around for about three years now. We've had tremendous success in terms of operator, channel partner, and developer adoption. And we in GSMA recognised that to really drive this and to drive the commercial model, we also needed that demand-side input. So with GSMA Fusion, we're working with enterprises across a number of different verticals — banking, media and entertainment, automotive, aviation, and so on — getting them to state what they require from network APIs that will drive commercial value. And those requirements feed into the Open Gateway ecosystem, driving operators and channel partners to make sure they expose these APIs so those solutions can be built. So I think that's the two sides coming together to fill that commercial gap that we have today.

Guy Daniels, TelecomTV (13:38):
Great. Thanks very much everyone. Nathan, you spoke earlier about not always needing to chase AI and using it correctly in the right layers. But a year ago, agentic was just starting to emerge — 18 months ago we were just starting to talk about agents. And for most of us it was, "What are AI agents?" And now we're all talking AI agents, agentic operations, protocols like MCP and agent-to-agent. I'd like to get a sense of how this is really impacting the work that's been going on for a number of years on APIs and platform-based models and economies.

Nathan Rader, Deutsche Telekom (14:20):
Yeah. I mean, we did address this in the CAMARA project and in cooperation with GSMA Open Gateway — we released a white paper that tries to describe how we as an industry see this. In general, at this point in time, the white paper is saying that MCP is going to be very important for people and agents to consume the APIs. But in order for that to work, we have to have the fundamental ecosystem that is being defined by Open Gateway and the standardised APIs being defined by CAMARA. Those building blocks need to be put in place first — and then MCP, agent-to-agent, can take and start consuming those. Because it just won't work if every telco's got a different setup. So that's kind of where we really see this heading at this point in time.

(15:17):
But I don't think we'll see it this year. Maybe next year we'll start seeing the first MCPs come about. I know Nokia has done some things, I know Telefónica has done some things, but I think we're still in early stages — not the "let it loose for agents and go." Now, I also think we have an opportunity as an industry to influence how some of these agents work. We have a lot of interesting capabilities in our networks that we should look into. One of those may be actually saying, "Okay, can we take and use the phone number?" Everybody's talking about these agents wanting to act on your behalf. Well, why can't we do exactly like we do with our phones and watches today — assign the agent your phone number and let them act on your behalf.

(16:06):
We have all of those capabilities to start doing that, and not only that — with things like number verification, we can even then authenticate that agent using your phone number to make sure that they're truly allowed to act on your behalf. So I think there are some interesting things ahead when the agents arrive.

Guy Daniels, TelecomTV (16:23):
Great. I can't wait, quite honestly. Bring it on, Raman.

Raman Mistry, GSMA (16:28):
Yeah. The agentic side of things changes the dynamics of how things are done. With APIs today, you've got the human in the loop because a developer manually wires those in. In the new world of agentic, potentially these are discoverable by agents and it's a machine-to-machine interaction with very little human in the loop. So the way that evolves has to be thought about carefully. MCP sits, I guess, as the layer between the agent and the CAMARA APIs in the background. And I think we're still at that nascent stage where these things still have to be thought through, but it does change the dynamics of potentially how these solutions will be built.

Guy Daniels, TelecomTV (17:20):
And Diego, this is also going to change the shape of network traffic, isn't it? And the way traffic flows?

Diego Lopez, Telefónica (17:27):
I don't know. I mean, since this session is about throwing water on things... If you think about it, MCP — we call it a protocol, but MCP is not actually... I mean, it's a framework for describing how to interact with tools. But at the end, the interaction will still be an API call most probably. So I'm not sure there's going to be a fundamental change in traffic shape. The fundamental change is going to be in volume. And then the challenge, as it was discussed in earlier sessions, is about identity, about making sure that when this API call comes from an agent, you are able to trace it back, make it accountable, make it chargeable.

Guy Daniels, TelecomTV (17:27):
So trying to make them accountable and therefore trying to make them monetisable and trace it back.

Diego Lopez, Telefónica (32:49):
Exactly. The moment I know that it's you who are using it, then I can ask you for your money — otherwise it's complicated.

Guy Daniels, TelecomTV (32:55):
So if I take a step back, why is it so complicated? Is it a pure scale issue? A speed issue?

Diego Lopez, Telefónica (33:03):
I would say that right now the way in which we are working — basically you are providing a credential to a person or to a role — is too coarse if you want to make this work in the way in which relationships are going to be complicated, automated, happening potentially in milliseconds or tenths of seconds. It's like certificates. We are used to certificates, but certificates are something that you get and they're valid for four months minimum.

Guy Daniels, TelecomTV (33:39):
Okay. And we know the problems with certificates.

Diego Lopez, Telefónica (33:41):
Yes.

Guy Daniels, TelecomTV (33:42):
David, your chance to fly the standards flag here. Is this ETSI to the rescue — standard policy to the rescue? What are you being asked to do in this area?

David Boswarthick, ETSI (33:55):
Yeah, I would love to say ETSI to the rescue — that's always our motto. But things are changing so quickly. And I think when you said, what is the challenge — is it scale? Is it the unknown? I think it's the speed of change and the unknown parameters. For the past five or six years in ISG MEC, we've been working on APIs for basically humans. Now we have AI coming into the network, coming in as a user of network resources. Our members don't know what the use cases will be or what the financial model will be. So you have to try something, see if it works. If you get volume of traffic, you probably need to readjust your financial model. The speed of change and the unknown seem like the biggest factors. Inside ETSI, we're trying to transform.

(34:39):
Traditional standards — we've been around for 30-plus years, paper, Word, PDF, lots of text. AI agents could consume that very quickly as training data, but it's not the right format for the AI generation. So what we're thinking about is how can we make our standards machine readable? How can we do much more work on open source? We have software development groups in ETSI alongside our traditional standards groups. So we're trying to predict the next change, what's needed next. And it seems to be all about software, all about rapidity of releases. A generation is ten years, a release is 18 months in 3GPP. Software needs much faster iteration. So it's about how can we make our methods, our formats, and our tools much quicker for the next generation.

Guy Daniels, TelecomTV (35:28):
I feel we're always having to play catch-up here.

David Boswarthick, ETSI (35:31):
Not until recently. 2G, 3G, 4G — fine. 5G — okay, quite difficult. 6G — again, speed of change, the interjection of AI, unknown business cases and use cases. It's a lot to play with.

Guy Daniels, TelecomTV (35:46):
Nathan, do you model ahead and say, look, the way this traffic's going at the moment, the way agent usage is starting out — it's quite nascent at this stage — it could go this way. It's going to have impact X, Y, Z. It sounds like it could be quite a challenge.

Nathan Rader, Deutsche Telekom (36:02):
Yeah, it could be. I don't think we know yet how the agents will change the traffic flow. But as Diego said, it shouldn't really change it that much fundamentally. There are still just going to be API calls coming in. Now the question is, do they come at higher frequency, higher volume? Well, that's really just a matter of designing our exposure platform to handle it. APIs are not new — Google, Amazon, everybody's running everything off API calls and they're able to handle Black Friday sales and things like that. So a few telco APIs shouldn't be a real challenge to solve. Our bigger problem is most likely in our own network and how fast our network equipment can handle it, but that will be up to each of us to ensure we're dimensioning our networks properly.

(36:56):
And maybe we've got to cache a little bit just to be able to protect some of the older network equipment, but it's just architecture and design at that point.

Guy Daniels, TelecomTV (37:07):
Very positive comment. I'm liking the positivity here. We threw cold water on it at the beginning, but we're surfacing again now. Having heard what we've said, any more questions from our audience? As we approach the end of our event, I'd love to get more audience participation if you so desire. Any questions, Tony? No? Are we all totally enthralled by the conversation? All right, let's carry on. Sorry, Tony, you have to sit back down again.

Nathan Rader, Deutsche Telekom (37:31):
Thanks for standing up for us.

Guy Daniels, TelecomTV (37:31):
So look, we've only got about five minutes of this session left. Nathan, you've spoken about some key APIs that are gaining traction and looking positive. Perhaps we could just have a look at what we expect to see over the next 12 months or so — what we think is going to be commercially attractive for that layer three, that exposure layer for developers, and consequently what action telcos and the ecosystem should be taking now to support and further that. Nathan, do you want to—

Nathan Rader, Deutsche Telekom (38:11):
Yeah, I mean, I think number verify two — particularly the verify portion of it — is going to be the one that's driving almost all the volume and revenue in the next 12 months. There will be a few others. But the one that's probably the most interesting and potentially the most impactful is the second endpoint that comes with number verify two — and that's number verify retrieve. That's basically the ability to use that not only for companies to get your phone number, but actually to get to the point of single-click login. So literally one button — log in with phone number, click consent, and go. And that becomes, I think, a game changer for user experience in terms of signing up for new accounts and authenticating yourself with one click instead of logging in, typing in a password, clicking through some one-time passwords.

(39:09):
Even that is still going to be quicker. So I think that's going to be the one where we see the most interesting uptake as developers start to realise that it's a great user experience.

Guy Daniels, TelecomTV (39:19):
It could be a big, big market for that one. David, what should telcos be doing?

David Boswarthick, ETSI (39:25):
From a standards perspective, it's really about focusing and avoiding fragmentation as always. We keep on seeing different standards organisations popping up and doing AI and doing data. The operators and even the vendors don't have a lot of resources to dedicate to standardisation. So really focus. If good work is happening in GSMA, let's focus on GSMA. If foundational level work is happening in ETSI, that's great — pre-standardisation to bring into 3GPP. But really concentrate effort, collaborate, and avoid fragmentation. Don't start a new forum just because it's easier. Try and make what you have work, build out from the foundation and then move forward.

Guy Daniels, TelecomTV (40:03):
Great. Thanks, David. And Raman, what's your outlook for the industry?

Raman Mistry, GSMA (40:05):
Again, I probably agree with both here. In terms of what Nathan was saying about number verify — we have a task force within GSMA on silent number authentication and it's a lot more secure, the user experience is far superior, so we're seeing a lot of momentum around those types of capabilities. And from a standardisation perspective, I know within CAMARA there's a group now looking into MCP and how that might impact the whole ecosystem. Within GSMA, we're looking at building a sandbox, a proof of concept around MCP as well. So there's a lot happening in the industry, but as I said earlier, it's still fairly nascent. I think through this experimentation and working through some of these standards that are coming to the fore, we'll get to some kind of solution that fits everyone.

Guy Daniels, TelecomTV (41:04):
Have you still got an education job to do with a lot of telcos to get them on board? Because we don't want fragmentation — we need telco-wide, unified solutions here.

Raman Mistry, GSMA (41:16):
Yeah. There's always that. From a supply side, we're working across the board, globally with all the operators to get them to come together around exposures and network APIs. And we've done a great job, but there is still work to do and still a number of markets out there that still need it. But the good thing is, I think Open Gateway has been a success and there's been a lot of momentum around it, and we can look to that as a proof point for why you need to do it. And talking about the monetisation value — connectivity's got maybe 2% growth rate, wherever you put it. The promise of having APIs, whether in agentic form or some other form, and building new innovative services, is the monetisation goal for a lot of these operators.

Guy Daniels, TelecomTV (42:12):
Great. Thanks very much. And Diego, we know which API is looking towards commercial success for you — what do we need to do?

Diego Lopez, Telefónica (42:19):
What Nathan has mentioned is about leveraging the trust. The implicit trust is probably the low-hanging fruit. But there are two things that are important for the mid to long term. One is about semantic models — we are going to expose data and make data available. The idea that data from different operators is not necessarily the same and not exposing exactly the same format is not necessarily fragmentation — it can have to do with legislation, with the culture in the countries they're operating in. But making them semantically compatible is quite important, and we are working on that — building a semantic framework for this. And the second is about providing mechanisms for openly composing things. Right now, the offers of agents are essentially "here is my agent playground, use it because there is nothing else." The point is that we should be able to provide users the possibility of saying, "I want an agent from here, another agent from there." And we have the unique opportunity of providing the glue — the common playground — whatever you call it.

(43:38):
And that's not for the next six months, but for the coming two or three years. It is our duty, not only an opportunity. We must do it.

Guy Daniels, TelecomTV (43:49):
We must do it. Absolutely, Diego. Thank you very much. And Nathan, next year, let's hope we won't talk about APIs.

Nathan Rader, Deutsche Telekom (43:54):
That's right. And we'll talk about services. There we go. That's the message. That's what we need to do in the next 12 months.

Guy Daniels, TelecomTV (43:58):
We've got to leave it there because we need to start our next session, our final session. So as we get our next guests on the stage, let's give our panellists a big round of applause. Thank you very much indeed.

Please note that video transcripts are provided for reference only – content may vary from the published video or contain inaccuracies.

Panel Discussion

This panel discussion at DSP Leaders World Forum examines how telcos can execute on network API opportunities while addressing the challenge of limited commercial traction. Deutsche Telekom’s Nathan Rader advocates focusing on API monetisation before pursuing agentic operations and proposes a three-layer network stack approach, while the GSMA’s Raman Mistry reports that two-thirds of Open Gateway deployments centre on trust and security solutions. The industry experts, including David Boswarthick from ETSI and Diego Lopez from Telefónica also discuss how to complement rather than compete with hyperscalers through unique network-based capabilities.

Broadcast live 20 May 2026

Participants

CO-HOST

Nathan Rader

VP Service and Capability Exposure, Deutsche Telekom

David Boswarthick

Director of Strategy and Innovation, ETSI

Diego R Lopez

Senior Technology Expert, Telefónica and ETSI Fellow

Raman Mistry

Channel Partner Engagement Lead, GSMA Open Gateway