Ericsson
Ericsson (Telefonaktiebolaget LM Ericsson) is a Swedish multinational networking and telecommunications equipment vendor headquartered in Kista, Stockholm. Founded in 1876, the company supplies mobile and fixed network infrastructure to communication service providers worldwide and operates across three product areas: Networks (5G RAN, 5G Core, Cloud RAN, transport), Cloud Software & Services (OSS/BSS, orchestration, billing, charging, analytics), and Enterprise Wireless Solutions (private 5G via Cradlepoint). Ericsson holds more than 60,000 granted patents and operates 21 R&D centers, with networks that carry roughly 40 percent of the world's mobile data traffic. In 2024 Ericsson and twelve major operators — AT&T, Bharti Airtel, Deutsche Telekom, KDDI, Orange, Reliance Jio, Singtel, Telefonica, Telstra, T-Mobile, Verizon, and Vodafone — closed Aduna, a 50:50 joint venture that aggregates CAMARA-aligned network APIs (SIM Swap, Number Verification, Quality on Demand, Device Location, Device Reachability, Scam Signal, Call Forwarding Signal, Connectivity Insights, OTP SMS) and exposes them through hyperscaler and CPaaS channel partners (Microsoft Azure Marketplace, Google Cloud, Vonage, Sinch, Infobip). Ericsson also owns Vonage (acquired 2022), which operates the public-facing developer portal for many of these network capabilities, and runs the Ericsson Intelligent Automation Platform (EIAP) for ORAN-aligned rApp development. Ericsson does not publish a single consolidated developer portal or canonical OpenAPI catalog at ericsson.com — its programmable surface is delivered indirectly through Aduna, Vonage, and channel partners, and most of its public GitHub presence is research tooling and infrastructure software (CodeChecker, CodeCompass, ecchronos) rather than developer-facing APIs.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Ericsson the way a machine reads it — 1 machine-readable artifact, 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 — Ericsson scores 7.9/100 (minimal), 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
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Ericsson
Each block below is one kind of artifact we hold for Ericsson. 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.
Security Posture 1
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.
Resources
Every other property we hold for Ericsson — 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.
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Company 10
The organization behind the API
Scroll within the panel for all 10 ·
Other 6
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/ericsson · machine-readable index on apis.io