{"id":17859,"date":"2026-05-06T11:17:41","date_gmt":"2026-05-06T11:17:41","guid":{"rendered":"https:\/\/www.europesays.com\/spain\/17859\/"},"modified":"2026-05-06T11:17:41","modified_gmt":"2026-05-06T11:17:41","slug":"telefonica-on-making-open-gateway-apis-agent-ready","status":"publish","type":"post","link":"https:\/\/www.europesays.com\/spain\/17859\/","title":{"rendered":"Telef\u00f3nica on making Open Gateway APIs agent-ready"},"content":{"rendered":"<p>\t\t\t501<br \/>\n\t\t\tTelef\u00f3nica is working with Nokia to test how AI agents can support the use of network APIs<\/p>\n<p>In sum \u2013 what to know:<\/p>\n<p>Open Gateway limits \u2013 Harmand said today\u2019s API-centric model works for atomic capabilities, but becomes structurally inefficient for complex, context-driven problems like fraud prevention.<\/p>\n<p>Intent-based orchestration \u2013 A2A and MCP shift developers from manually chaining APIs to expressing objectives (e.g., \u201cassess fraud risk\u201d), with agents dynamically discovering and composing network tools.<\/p>\n<p>Governance before scale \u2013 Commercial deployment depends less on technical viability than on trust frameworks, including agent authentication, authorization, privacy, and auditable controls.<\/p>\n<p>Earlier this month, <a href=\"https:\/\/www.telefonica.com\/en\/communication-room\/press-room\/telefonica-nokia-collaborate-accelerate-network-api-adoption-agentic-ai\/\" target=\"_blank\" data-type=\"link\" data-id=\"https:\/\/www.telefonica.com\/en\/communication-room\/press-room\/telefonica-nokia-collaborate-accelerate-network-api-adoption-agentic-ai\/\" rel=\"noreferrer noopener nofollow\">Telef\u00f3nica and Nokia announced a collaboration <\/a>to test how AI software agents could support the use of network APIs, as part of <a href=\"https:\/\/www.rcrwireless.com\/20230227\/5g\/major-telcos-move-to-open-network-apis-to-developers-to-drive-innovation-revenues\" target=\"_blank\" data-type=\"link\" data-id=\"https:\/\/www.rcrwireless.com\/20230227\/5g\/major-telcos-move-to-open-network-apis-to-developers-to-drive-innovation-revenues\" rel=\"noreferrer noopener nofollow\">the GSMA Open Gateway initiative <\/a>to standardize access to telecom network capabilities.<\/p>\n<p>Initial testing has focused on a fraud prevention use case in a lab environment. Telef\u00f3nica is using Nokia\u2019s Network Exposure Platform to expose network APIs and related functions \u2014 including SIM swap and device swap \u2014 while Nokia\u2019s Network as Code platform aggregates those capabilities for application developers through an Agent-to-Agent (A2A) format. The work centers on two emerging protocols: Agent-to-Agent Protocol (A2A), which enables AI agents to coordinate tasks, and Model Context Protocol (MCP), which provides a standardized way for AI systems to access external tools and data.<\/p>\n<p>Telef\u00f3nica Core and Platforms Senior Manager Alex Harmand told RCR Wireless News that today\u2019s Open Gateway model works well for individual, \u201catomic\u201d network functions, but becomes less effective when developers need to solve more complex, context-driven problems. \u201cFor example, in an anti-fraud scenario, we must manually orchestrate multiple APIs \u2014 roaming verification, SIM swap, device swap, and others,\u201d he said. \u201cToday, there is no single anti-fraud API; the client must call each specialized API individually and implement the risk logic themselves.\u201d<\/p>\n<p>That approach, he explained, requires operators to build and maintain an orchestration layer that embeds scoring logic, manages integrations, and handles versioning. Each new fraud signal \u2014 such as a scam indicator \u2014 can trigger code changes and new API releases, with much of the intelligence remaining fixed in the integration layer.<\/p>\n<p>\u201cA2A and MCP shift this model from contract-driven orchestration to intent-driven execution,\u201d Harmand said. Instead of calling predefined APIs, developers could express a higher-level objective \u2014 such as \u201cassess fraud risk\u201d \u2014 and an AI agent would dynamically identify available tools, combine them, and adapt as new capabilities or versions are introduced. \u201cIn short, we move from static API composition to adaptive, intent-based capability orchestration,\u201d he said, arguing that the approach could reduce complexity and improve resilience as network services evolve.<\/p>\n<p>Telef\u00f3nica and Nokia said they plan to test additional use cases and share insights with the broader industry, though Harmand noted that commercial deployment will depend largely on customer demand. \u201cTechnically, the use case is viable today,\u201d he said. \u201cThe core fraud-prevention logic works, and the agent can already reason over the available capabilities and compose them effectively.\u201d<\/p>\n<p>Before deployment, however, Harmand said several areas must be fully addressed, particularly around trust and governance. These include strong authentication and authorization for agents, enforceable policy controls and auditability for fraud-related decisions, and clear privacy and consent mechanisms.<\/p>\n<p>\u201cThe biggest risk is not autonomy itself,\u201d Harmand added, \u201cbut ensuring control, trust, and accountability once autonomy is introduced.\u201d<\/p>\n<p>He emphasized that agents must operate strictly within operator-defined constraints and should never be \u201cself-authorizing entities.\u201d<\/p>\n<p>\u201cThe critical failure point would be introducing autonomous coordination without a robust governance and trust framework,\u201d he said. \u201cBut when these controls are properly engineered, agentic systems do not reduce operator control \u2014 they elevate the abstraction layer while preserving authority over execution.\u201d<\/p>\n","protected":false},"excerpt":{"rendered":"501 Telef\u00f3nica is working with Nokia to test how AI agents can support the use of network APIs&hellip;\n","protected":false},"author":2,"featured_media":17860,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[124],"tags":[155],"class_list":{"0":"post-17859","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-telefonica","8":"tag-telefonica"},"_links":{"self":[{"href":"https:\/\/www.europesays.com\/spain\/wp-json\/wp\/v2\/posts\/17859","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/spain\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/spain\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/spain\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/spain\/wp-json\/wp\/v2\/comments?post=17859"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/spain\/wp-json\/wp\/v2\/posts\/17859\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/spain\/wp-json\/wp\/v2\/media\/17860"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/spain\/wp-json\/wp\/v2\/media?parent=17859"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/spain\/wp-json\/wp\/v2\/categories?post=17859"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/spain\/wp-json\/wp\/v2\/tags?post=17859"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}