API

Network APIs expose telecom capabilities — such as quality of service, location, device status, and authentication — to developers and enterprises through standardized programmable interfaces. Industry initiatives including GSMA Open Gateway and the CAMARA project aim to make these capabilities consistent across operators, turning the network into a platform that applications can call directly. For operators, APIs represent a route to revenue beyond connectivity; for enterprises and developers, they offer programmable access to network features once locked inside carrier systems. Standards bodies including TM Forum and 3GPP continue to shape how these interfaces are defined and monetized. This channel tracks network API standards, operator and hyperscaler partnerships, monetization models, and real deployments, with analysis of where programmable networks are gaining commercial traction and where adoption still lags behind the ambition.

China Telecom, China Mobile, and China Unicom have each unveiled token-based service plans, ecosystem alliances, and commercial pricing structures that reframe what it means to be a telecom provider in the AI era. This is not a pilot program or a speculative roadmap. It is a structural shift in how network operators intend to generate revenue, compete for enterprise customers, and position themselves at the center of the AI economy — driven by a greater than 1,000-fold surge in daily token consumption across China between early 2024 and March 2026.
BT is set to launch commercial 5G network slicing services before the end of summer 2026, marking a significant milestone for the UK's 5G Standalone market. Built on Ericsson's dual-mode 5G Core and underpinned by dynamic slice selection via NSSF and programmable network access through NEF APIs, BT's offer targets both enterprise and consumer segments. With 5G SA coverage already reaching 50 million people and a 90% population threshold defining national availability, BT is positioning slicing as a credible, SLA-backed connectivity service — not a proof-of-concept.
Circles and OpenAI have reached a major milestone in building the world's first AI-native telco stack, moving beyond legacy BSS/OSS bolt-on approaches. Flagship products CareX and Xplore IQ deliver measurable outcomes — including 85% autonomous query resolution and a 22% ARPU uplift in Singapore deployments. Built on a multi-agent architecture and OpenAI's API platform, the stack enables telecom operators across 14 countries to automate customer operations and drive proactive revenue monetization without rebuilding infrastructure from scratch.
Vodafone Business and Google Cloud expanded their $1 billion, ten-year partnership with two launches aimed squarely at small and mid-sized businesses: a managed detection and response service and an agentic AI concierge. Vodafone Business and Google Cloud are packaging hyperscaler security analytics and agentic AI into carrier-delivered services that SMBs can adopt quickly. The launch markets, technology choices, and managed wrap indicate a pragmatic path to better protection and always-on customer engagement. Leaders should pilot now with tight KPIs, validate compliance early, and build an integration roadmap that scales across markets as the offer expands through Europe.
Intel and Google expanded a multiyear partnership that doubles down on Xeon CPUs and custom infrastructure processing units to scale AI with better efficiency and predictability. Google committed to multiple generations of Intel Xeon for AI, inference, and general-purpose workloads across its global cloud. The latest Xeon 6 processors are already powering Google Cloud’s workload-optimized instances, including C4 and N4, to coordinate large-scale training, serve latency-sensitive inference, and run mainstream compute. In parallel, the companies will broaden co-development of custom ASIC-based IPUs that offload networking, storage, and security from host CPUs to improve utilization and deliver more stable performance at hyperscale.
ETSI has introduced OpenOP Release 1 as an open-source operator platform for telco cloud, designed to standardize capability exposure and federation at the edge while creating a practical bridge from 5G-Advanced to early 6G experimentation. Networks are becoming software-first and distributed, but operators still face fragmented exposure of network capabilities and inconsistent approaches to multi-operator edge. OpenOP targets this gap with a standards-aligned, open implementation that lets developers consume telecom capabilities via CAMARA APIs and deploy applications across federated edge zones. Release 1 provides a working, end-to-end baseline with integrated components for exposure, orchestration, federation, and AI-assisted intent, suitable for hands-on testing and integration.
AT&T’s new collaboration with Cisco and NVIDIA signals a decisive shift from cloud-centric AI to network-driven edge intelligence for enterprise operations. Enterprises want real-time decisioning without shipping sensitive data to distant clouds, and operators need a scalable way to deliver it. By combining AT&T’s dedicated IoT core with Cisco’s mobility services platform and NVIDIA-powered AI infrastructure, the trio is packaging deterministic connectivity, near-device inference, and policy enforcement into a single, operator-grade platform. The promise: lower latency, tighter data control, and a path to production for AI at industrial scale.
AT&T’s five-year, $250 billion U.S. network commitment sets the tone for the next phase of fiber, 5G, and satellite convergence as traffic, AI workloads, and resilience requirements climb sharply. The 2026–2030 window aligns with the industry’s transition into 5G-Advanced (3GPP Release 18/19), the scaling of edge AI, and increased cloud traffic between homes, enterprises, and hyperscalers. Data growth is no longer linear, and the cost of downtime is rising. Large, front-loaded builds in fiber and 5G Radio Access Network (RAN), paired with new satellite overlays, are how national carriers will chase coverage, performance, and reliability targets simultaneously.
TELUS Digital is using Mobile World Congress 2026 to move the AI-in-telecom conversation from pilots to proven production at scale. TELUS Digital reports processing more than two trillion tokens in 2025 through its Fuel iX generative AI platform for TELUS operations and customers. The portfolio spans AI for customer experience, application safety, and network modernization—built and battle-tested within TELUS before client rollout. The Network Design Services practice applies AI to planning and optimization while charting a path from legacy network stacks to cloud-native, automated environments.
Nokia and Amazon Web Services (AWS) are bringing agentic AI to 5G-Advanced network slicing, moving closed‑loop, intent-based services from PowerPoint to live pilots with du and Orange. The partners unveiled an agentic AI-powered slicing solution that fuses Nokia’s RAN-to-core slicing, AirScale radio, and MantaRay SMO with AWS’s Bedrock AI platform and EKS Hybrid Nodes to turn external context—events, traffic, maps, weather—and live network KPIs into real-time policy decisions. The result is adaptive, premium slices provisioned when and where they’re needed, without manual reconfiguration.
OpenAI is reportedly building a portfolio of AI-native devices, signaling a push beyond software and into ambient, multimodal computing that will touch homes, workplaces, and networks. Multiple reports indicate OpenAI has over 200 people developing a family of AI-enabled hardware, with a smart speaker expected to debut first. Early guidance points to a price in the $200–$300 range and a ship window no earlier than February 2027. The device is said to include a camera to capture contextual information about users and surroundings—an explicit bet on multimodal AI that fuses voice, vision, and environment for richer interactions.
The UK government signalled a rapid escalation of online safety measures that will bring AI chatbots squarely under the Online Safety Act and could introduce an under‑16 social media ban as early as this year. Ministers plan to amend the Online Safety Act 2023 so one‑to‑one interactions with AI systems fall within scope of illegal and harmful content controls. The government wants providers of large language model (LLM) assistants and agentic chatbots to implement safety‑by‑design, including stronger filtering, red‑teaming, abuse detection, and rapid takedown procedures for sexualised or otherwise illegal outputs.

Frequently Asked Questions

What is GSMA Open Gateway, and why was it created?
GSMA Open Gateway is an industry-wide initiative, backed by the GSMA, the trade body representing mobile operators globally, and dozens of major carriers, designed to standardize network APIs across operators and countries. Before this initiative, a company wanting to use a SIM swap detection API to prevent account-takeover fraud would typically need separate technical integrations and commercial agreements with every carrier in every market it operated in, an approach that didn’t scale well for global digital businesses like banks or ride-sharing platforms. Open Gateway defines a common technical specification for these APIs so a single integration works consistently across participating operators worldwide, dramatically reducing the engineering and business development overhead for any company wanting to build services on top of carrier network data.
Why do telecom companies want to expose network APIs to outside developers?
Exposing network APIs gives carriers a new revenue stream that doesn’t depend on selling more raw data or voice minutes, an increasingly commoditized, low-margin business. Instead, operators can charge for premium, differentiated capabilities, like verified caller identity for fraud prevention, real-time network quality guarantees for a specific application, or device location data for logistics and delivery tracking, turning the network itself into a monetizable platform. This mirrors a broader strategic shift across the industry, often summarized as moving from selling bandwidth to selling outcomes, where operators position themselves as infrastructure partners for other industries’ digital products rather than purely as connectivity providers competing on price. It also opens partnerships with software companies that wouldn’t otherwise have a direct commercial relationship with an operator at all.
What are some real-world examples of telecom network APIs in use today?
Some of the most established use cases include number verification, used heavily by banking and fintech apps to confirm a user genuinely controls the phone number tied to their account before allowing a transaction; SIM swap detection, which flags when a phone number has recently been transferred to a new SIM, a common signal of an account-takeover attempt; and location APIs, used by logistics and delivery companies for real-time tracking, or by other services for geofencing-based features. Newer, more specialized examples are emerging too, including quality-on-demand APIs that let an application request guaranteed network performance for a specific session, useful for video calls or cloud gaming, effectively giving developers programmatic access to capabilities like network slicing without negotiating a direct deal with the underlying carrier.
How do network APIs relate to network slicing and monetization?
Network slicing creates the actual underlying capability, a dedicated, performance-guaranteed virtual network for a specific purpose, while network APIs are often the mechanism by which a third-party developer actually requests and uses that capability programmatically, without needing to understand or manage the underlying slicing infrastructure directly. A quality-on-demand API, for example, might let a video conferencing app request guaranteed low latency for an important call, with that request fulfilled behind the scenes by the operator’s slicing infrastructure. This pairing is central to how operators are trying to monetize their 5G Standalone investments: slicing creates differentiated network capabilities, and APIs are the commercial and technical interface that makes those capabilities accessible and billable to outside developers.
What’s stopping network APIs from being adopted faster?
Adoption has been slower than initial industry enthusiasm suggested, for a few recurring reasons. Developers building global products need consistent behavior across operators and countries, and while standardization initiatives like Open Gateway aim to solve this, achieving true consistency across dozens of carriers, each with their own legacy systems and commercial priorities, takes time. There’s also a chicken-and-egg dynamic: developers are hesitant to build products around APIs that aren’t yet universally available, while operators are cautious about investing heavily in API infrastructure without proven developer demand. Pricing adds another layer of friction, since operators are still experimenting with how to price access in a way that’s attractive to developers while still generating meaningful revenue relative to infrastructure cost.
Who are the typical customers building on top of telecom network APIs?
Customers span a range of industries, but financial services and fraud prevention have been the earliest and most consistent adopters, using number verification and SIM swap detection to reduce account-takeover and transaction fraud. Logistics, delivery, and ride-sharing companies are major users of location-based APIs for real-time tracking and route optimization. Gaming and entertainment companies are increasingly interested in quality-on-demand APIs to guarantee performance for latency-sensitive applications like cloud gaming. Beyond individual companies, aggregator platforms have emerged specifically to combine APIs from multiple operators into a single access point, letting developers integrate once and reach users across many carriers and countries without managing separate relationships with each one.
Are network APIs secure, and who controls access to sensitive data like location?
Security and access control are central design considerations for network APIs, given the sensitive nature of data like location or SIM status. Access is generally tightly controlled through authentication and authorization systems, and most operators only expose specific, limited capabilities through these APIs rather than raw access to underlying network or subscriber data. Consent mechanisms are also typically built in, particularly for anything involving an individual’s location or personal data, often requiring an explicit user opt-in before that data can be shared with a third-party application. This remains an evolving area, and as more operators expose more capabilities through these interfaces, regulators and privacy advocates are paying closer attention to how consent is obtained across different countries with different privacy law standards.

Your Brand. Our Intelligence Tools.

Capture leads at the point of evaluation. Talk to Us →

Sponsored by Palo Alto Networks
⚡ Utilities ⏱ 8 min ✓ Free
This tool is built and hosted by TeckNexus.
Launch Tool →
Whitepaper
This whitepaper explains how utilities can use secure AI-enabled private mobile networks to modernize operations, support distributed intelligence, improve resilience, and strengthen cybersecurity across critical infrastructure. It covers AI applications, private network advantages, zero trust principles, multilayered security architecture, and governance considerations for AI-ready utility environments....
Whitepaper
Non-terrestrial networks are rapidly evolving from experimental satellite systems into an increasingly important part of the global 5G connectivity landscape. This eBook, developed by Radisys in collaboration with TeckNexus, explores how 3GPP standardization, satellite architecture innovation, and software-driven network design are reshaping NTN deployment models. It examines the transition from...
Whitepaper
Private cellular networks are transforming industrial operations, but securing private 5G, LTE, and CBRS infrastructure requires more than legacy IT/OT tools. This whitepaper by TeckNexus and sponsored by OneLayer outlines a 4-pillar framework to protect critical systems, offering clear guidance for evaluating security vendors, deploying zero trust, and integrating IT,...
Scroll to Top