Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Nokia website screenshot

Nokia

Nokia (Nokia Oyj) is a Finnish multinational telecommunications, information technology, and consumer electronics corporation headquartered in Espoo, Finland. Nokia is a leading vendor of carrier-grade network equipment for communication service providers (CSPs), webscalers, and enterprises across mobile (5G/6G RAN, Core), fixed (broadband, fiber), IP (Service Router OS / SR Linux), optical (WaveSuite, 1830 PSS/PSI), submarine cable, and cloud and network services. Nokia's developer surface spans (1) the Network Services Platform (NSP) automation suite, (2) the SR OS / SR Linux network operating systems with the pySROS SDK and YANG models for the 7x50 platform, (3) WaveSuite optical management REST APIs with Swagger documentation, (4) the CAMARA-compliant Network as Code platform exposing 16+ standardized network APIs (Quality on Demand, Device Location, SIM Swap, Number Verification, KYC, Geofencing, Slicing) for B2B and B2C developer consumption, and (5) the Network Exposure Platform that enables operators to expose their own network capabilities to developers. Nokia also operates Nokia Technologies (licensing), the Bell Labs research division, and a broad open-source presence (600+ GitHub repos) including TTCN-3 tooling (ntt), Corteca CLI, Moler test framework, and YANG models.

human only

More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.

Kin Score

API Evangelist profiles Nokia the way a machine reads it — 8 machine-readable artifacts across 6 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 — Nokia scores 21.1/100 (emerging), with a separate agent-readiness read of 0/100 (human only). 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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 21.1/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 7.4 / 20
Commercial Clarity 4.2 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 8.8 / 10
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Nokia

Each block below is one kind of artifact we hold for Nokia. 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 6

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.

Nokia Network as Code Platform

CAMARA-compliant, production-ready Network APIs exposing 5G core and RAN functions through standardized northbound interfaces. Includes Quality on Demand, Device Location (Verif...

Nokia Network Services Platform (NSP) API

REST-based automation and assurance API for Nokia's multilayer (IP + optical) Network Services Platform. Provides programmable model-driven service orchestration, inventory, fau...

Nokia SR OS pySROS SDK and YANG Models

pySROS is the official Python SDK for model-driven configuration, operational data retrieval, and automation against Nokia SR OS devices (7x50 SR/IXR/XRS/MG and family). Backed ...

Nokia SR Linux

Modern, Linux-based, fully model-driven network operating system for data-center and service-provider routing. SR Linux exposes a gNMI / gNOI management surface, a NETCONF inter...

Nokia WaveSuite Optical REST APIs

Optical networking REST APIs (Swagger-documented) across the WaveSuite portfolio — WaveSuite-NOC, WaveSuite Resource Control, WaveSuite Optimizer, Planner, Service Enablement, a...

Nokia Network Exposure Platform

Operator-facing platform that enables CSPs to expose their own network capabilities as standardized CAMARA / GSMA Open Gateway APIs to developers and aggregators. Sits beneath N...

Security Posture 2

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.

Nokia Corp Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Nokia Corp Vulnerability Disclosure

security.txt · contact published

SECURITY

Resources

Every other property we hold for Nokia — 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.

Documentation 2

Reference material describing how the API behaves

Access & Security 2

Authentication, authorization, and security posture

Learn 1

Tutorials, courses, talks, and written guidance

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

← All providers · Data indexed from github.com/api-evangelist/nokia-corp · machine-readable index on apis.io