More Information

Built on the standards the industry already agreed

TM Forum, CAMARA, 3GPP, ETSI and Mplify

Exosphere Agentic is grounded in the standards telecom already agreed, so your agents speak the industry's language from the first loop. Exosphere Agentic runs on Azure and integrates with the Microsoft AI platform, deployed into the customer's own tenant — so context, data and governance stay where they belong.

Updated 11 October 2026

TM Forum native, backend-neutral

TM Forum Open APIs are the contract. Exosphere Agentic reaches your systems through them, so it works over the BSS you already run, whoever built it.

Standard	How Exosphere Agentic uses it
GB922 SID (Information Framework)	The nouns of the telecom ontology: customer, product, service, resource and more
GB921 eTOM (Business Process Framework)	Process context for every loop, from inquiry to resolution
Open Digital Architecture (ODA)	Fast-moving engagement kept apart from stable systems of record, with Exosphere, the judgment layer inside Exosphere Agentic, governing what passes between them
Open APIs	Governed actions, for example TMF620 Product Catalog, TMF622 Product Ordering, TMF641 Service Ordering, TMF656 Service Problem, TMF666 Account and TMF678 Customer Bill
TMF921 Intent Management	Outcomes expressed as intent, validated against TM Forum's Intent Ontology

TM Forum's OpenAPI specifications, conformance test kits and reference implementations are published under Apache 2.0 unless stated otherwise.

CAMARA exposes the network. TM Forum runs the business around it.

CAMARA network APIs, such as Quality on Demand, SIM Swap and Number Verification, let developers and enterprises use network capabilities.
TMF931 Open Gateway Onboarding and Ordering composes TMF622, TMF637, TMF669 and TMF639, so network exposure has a commercial lifecycle.
3GPP SA5 covers network management and converged charging.
ETSI NFV and MEC describe virtualised and edge functions.
Mplify (formerly MEF) LSO covers partner ordering and trouble tickets across wholesale boundaries.

Exosphere Agentic connects these to the customer and the bill through the telecom ontology.

Network-side standards around Exosphere Agentic

flowchart TB
    DEV["Developers and enterprises"]
    subgraph EXPOSE["EXPOSURE"]
        C1["CAMARA network APIs<br/>QoD · SIM Swap · Number Verification"]
        C2["TM Forum Operate APIs<br/>TMF931 onboarding and ordering"]
    end
    subgraph EXO["EXOSPHERE AGENTIC"]
        E1["Telecom ontology<br/>SID meaning"]
        E2["TM Forum Open APIs<br/>order · inventory · assurance · bill"]
        E3["Governed MCP actions<br/>authorise · audit"]
    end
    subgraph PARTNER["PARTNER AND WHOLESALE"]
        P1["Mplify LSO<br/>partner order and trouble ticket"]
    end
    subgraph NETSIDE["NETWORK-SIDE STANDARDS"]
        NX["Operator network exposure"]
        G1["3GPP SA5<br/>management · charging"]
        G2["ETSI NFV and MEC<br/>virtualised and edge functions"]
    end
    DEV --> C1
    DEV --> C2
    C1 -->|"API calls"| NX
    C2 -->|"commercial lifecycle"| E2
    E1 --- E2
    E2 --- E3
    E3 --> P1
    E3 --> G1
    E3 --> G2
    classDef exos stroke:#0077B6,stroke-width:2px
    classDef std stroke:#005F8A,stroke-width:1px
    class E1,E2,E3 exos
    class C1,C2,P1,G1,G2 std

Exposure, partner and network standards meet the commercial lifecycle in one governed layer.

MCP in front of the Open APIs

Standards bodies are putting MCP in front of their APIs, and Exosphere Agentic is designed for exactly that:

TM Forum's ODA work treats MCP servers for the Open APIs as another API type, with governance and lifecycle management.
The AI-Native ODA Canvas declares MCP a first-class interface type.
Mplify LSO has added MCP servers for its seller-side APIs.
Microsoft has built an ODA Canvas on Azure and publishes its canvas assets openly, with reference operators for Azure API Management and Microsoft Entra ID. TM Forum Inform named Exos Systems among the early users of Azure's ODA Canvas implementation.

Exosphere adds the governed layer on top: which loop may use which tool, under which policy, with which approval, recorded end to end.

The AI-native ODA direction, layer by layer

flowchart LR
    subgraph TMF["AI-NATIVE ODA ROADMAP"]
        R1["BSS and OSS ontologies<br/>based on SID and eTOM"]
        R2["Agent-ready Open APIs"]
        R3["Agents triggered by<br/>real-time events"]
        R4["Human control at any level<br/>guardrails · audit trails"]
        R5["Sovereign-aware ODA"]
        R6["ODA as a data product<br/>for retrieval and graph"]
    end
    subgraph EXO["EXOSPHERE AGENTIC LAYERS"]
        X1["Telecom ontology<br/>SID ABEs as entity types"]
        X2["Governed MCP tools<br/>over TM Forum Open APIs"]
        X3["Event mesh<br/>in flight, not batch"]
        X4["Governed orchestration<br/>authorise · observe · audit"]
        X5["Deploys in the operator's<br/>own tenant"]
        X6["Grounding<br/>retrieval with citations"]
    end
    R1 --> X1
    R2 --> X2
    R3 --> X3
    R4 --> X4
    R5 --> X5
    R6 --> X6
    classDef exos stroke:#0077B6,stroke-width:2px
    classDef std stroke:#005F8A,stroke-width:1px
    class X1,X2,X3,X4,X5,X6 exos
    class R1,R2,R3,R4,R5,R6 std

Exos view: alignment with the direction of travel, not a conformance claim.

Autonomy is assessed, not claimed

TM Forum's Autonomous Networks model describes six levels, from L0 manual operation to L5 full autonomy. Levels are assessed with a standard methodology and independently validated, rather than self-declared.

Exosphere Agentic brings the same discipline to BSS loops: autonomy is set per action type, evidence moves it, and the operator approves every promotion and demotion. The levels serve as a reference point; the evidence does the talking.

Exos Systems is a TM Forum member and aligns to ODA. Standards bodies named here describe the context we work in; they are not an endorsement by those bodies.

Talk standards with Exos

Ask for the ontology briefing, book a demo, or open the library.