ETSI
ETSI, the European Telecommunications Standards Institute, is a not-for-profit standards development organisation headquartered in Sophia Antipolis, France, and one of only three bodies officially recognised by the European Union as a European Standards Organisation. With over 900 member organisations from more than 60 countries it standardises ICT across mobile, fixed, broadcast, IoT, security and emerging technologies, and it hosts the 3GPP Mobile Competence Centre. In the telecom value chain ETSI sits upstream of every operator and vendor: it does not run a network or sell connectivity, it writes the specifications that the network is built from. Its API posture is unusually open for a standards body. Every ETSI deliverable is downloadable free of charge without login from etsi.org/deliver, and the machine-readable API artefacts are published as BSD-3-Clause OpenAPI on two public GitLab instances, forge.etsi.org and labs.etsi.org, both of which serve an anonymous REST API. From those ETSI publishes the ISG MEC edge service APIs, the NFV SOL lifecycle and orchestration APIs, the ISG CIM NGSI-LD context information API, and open-source implementations including OpenCAPIF for 3GPP CAPIF, OpenSlice for TM Forum Open APIs, and an Operator Platform Open Exposure Gateway that exposes northbound CAMARA APIs. What is member-gated is participation, not publication: portal.etsi.org, working documents, drafting and voting sit behind ETSI membership, while the finished standards and their OpenAPI are open to anyone. ETSI itself is not a GSMA Open Gateway operator and not a CAMARA member organisation; it reaches CAMARA through liaison and through its own open-source code.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles ETSI the way a machine reads it — 30 machine-readable artifacts across 24 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — ETSI scores 52.1/100 (developing), with a separate agent-readiness read of 61/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile ETSI
Each block below is one kind of artifact we hold for ETSI. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 24
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
ETSI MEC 011 Edge Platform Application Enablement API
The Mp1 reference point between MEC applications and the MEC platform, standardised in ETSI GS MEC 011. Covers MEC service registration, deregistration, discovery and event noti...
ETSI MEC 012 Radio Network Information API
The Radio Network Information Service (RNIS) defined in ETSI GS MEC 012, exposing up-to-date radio network conditions, measurement reports, cell change and carrier aggregation i...
ETSI MEC 013 Location API
The MEC Location Service defined in ETSI GS MEC 013, providing network-derived location of user equipment and of radio nodes, zone and access-point occupancy, distance calculati...
ETSI MEC 014 UE Identity API
The UE Identity API from ETSI GS MEC 014, which lets a MEC application register a UE identity tag with the MEC platform so that traffic filtering rules can be applied to a speci...
ETSI MEC 015 Traffic Management APIs
The two traffic-management APIs of ETSI GS MEC 015: Bandwidth Management, which lets applications register bandwidth requirements and priorities with the MEC platform, and Multi...
ETSI MEC 016 UE Application Interface API
The Mx2 reference point from ETSI GS MEC 016, used by a device-side application to discover which MEC applications are available in the system and to request instantiation or te...
ETSI MEC 010-2 Application Package and Lifecycle Management APIs
ETSI GS MEC 010-2 Part 2 application package management, application lifecycle management and application grant APIs, used by an operations support system to onboard, instantiat...
ETSI MEC 021 Application Mobility Service API
The Application Mobility Service defined in ETSI GS MEC 021, which coordinates the relocation of a running application instance and its user context between MEC hosts as a devic...
ETSI MEC 028 WLAN Information API
The WLAN Access Information Service from ETSI GS MEC 028, exposing access-point, station and measurement information from Wi-Fi networks to edge applications alongside the cellu...
ETSI MEC 029 Fixed Access Information API
The Fixed Access Information Service from ETSI GS MEC 029, extending MEC information exposure beyond mobile to fixed broadband access networks including PON and cable, so edge a...
ETSI MEC 030 V2X Information Services API
The V2X Information Service defined in ETSI GS MEC 030, providing predicted quality of service, provisioning information and multi-operator V2X message distribution for connecte...
ETSI MEC 033 IoT API
The IoT API from ETSI GS MEC 033, defining how IoT device registration, IoT platform selection and device-to-platform association are managed by a MEC system so that IoT traffic...
ETSI MEC 040 MEC Federation Enablement API
The MEC Federation enablement API from ETSI GS MEC 040, which lets edge systems operated by different providers discover one another, exchange availability zone and system infor...
ETSI NFV SOL002 / SOL003 VNF Lifecycle, Fault, Performance and Package Management APIs
The RESTful protocols and data models of ETSI GS NFV-SOL 002 (Ve-Vnfm reference point, between a VNF and its VNF manager) and ETSI GS NFV-SOL 003 (Or-Vnfm reference point, betwe...
ETSI NFV SOL005 Os-Ma-nfvo Network Service Management APIs
The RESTful protocols and data models of ETSI GS NFV-SOL 005 on the Os-Ma-nfvo reference point, between an OSS/BSS and an NFV orchestrator. Covers network service descriptor man...
ETSI NFV SOL009 NFV-MANO Management APIs
The RESTful protocols and data models of ETSI GS NFV-SOL 009 for managing the NFV management-and-orchestration functions themselves, covering NFV-MANO configuration and informat...
ETSI NFV SOL011 Or-Or Multi-Administrative-Domain APIs
The RESTful protocols and data models of ETSI GS NFV-SOL 011 on the Or-Or reference point, used between NFV orchestrators in different administrative domains for nested network ...
ETSI NFV SOL012 Policy Management API
The RESTful protocol and data model of ETSI GS NFV-SOL 012 for policy management across NFV management and orchestration, covering policy transfer, activation, deactivation, del...
ETSI NGSI-LD API (ISG CIM)
The NGSI-LD API standardised by ETSI ISG CIM in GS CIM 009, a JSON-LD context information management API for entities, attributes, relationships, subscriptions, temporal queries...
ETSI OpenCAPIF (3GPP CAPIF TS 29.222) APIs
The ETSI Software Development Group implementation of the 3GPP Common API Framework, TS 29.222. Harvested here are the API Invoker Management, API Provider Management, Access Co...
ETSI OpenSlice CAMARA-as-a-Service QoD Provisioning API
A CAMARA Quality on Demand (QoD) Provisioning API implementation shipped as an add-on to ETSI OpenSlice. It wraps a running TM Forum service inventory entry so an operator can e...
ETSI Operator Platform Open Exposure Gateway API
The Open Exposure Gateway of the ETSI Operator Platform SDG, implementing the Open Exposure Gateway role defined by the GSMA Operator Platform Group. It exposes northbound CAMAR...
ETSI OpenSlice TM Forum Open APIs
ETSI SDG OpenSlice is an open-source service-based OSS delivering Network as a Service, and it exposes its catalog, ordering and inventory surface as TM Forum Open APIs. The doc...
ETSI MEC Sandbox / EdgeNative Connector
A hosted, free interactive environment where developers exercise live ETSI MEC service APIs against emulated 4G, 5G and Wi-Fi network scenarios with moving user equipment. It se...
Scroll within the panel for all 24 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
etsi-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Etsi Webhooks
ASYNCAPISecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for ETSI — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 6
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 3
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 5
The organization behind the API
Other 17
Properties that don't map to a standard resource type
Scroll within the panel for all 17 ·
← All providers · Data indexed from github.com/api-evangelist/etsi · machine-readable index on apis.io