AxyomCore

Telecom infrastructure software vendor, styled Axyom.Core, supplying cloud-native 4G and 5G mobile core and RAN network functions (CNFs) that run inside communications service provider networks. Product lines cover 4G core, Femto core, security gateway, RAN and full-MVNO deployments, with Red Hat OpenShift support. Part of Lumine Group following a carve-out from Casa Systems. NO PUBLIC API SURFACE: the company sells into operator networks through RFP and direct engagement, and publishes no developer portal, API documentation, or machine-readable contract. That is an absence of a PUBLIC interface, not an absence of APIs — mobile core network functions are API-driven by construction, but those interfaces reach customers under operator contracts rather than a public developer program.

AxyomCore is profiled on the APIs.io network. Tagged areas include Telecommunications, 5G Core, 4G/LTE Core, RAN, and Mobile Network Functions.

AxyomCore’s developer surface includes support, engineering blog, and 2 more developer resources.

🌐 Visit website 📡 Source on GitHub
1.1/100 minimal ▬ flat Agent 0/100 human only Full breakdown ↓
scored 2026-08-20 · rubric v0.12.0
0 APIs
Telecommunications5G Core4G/LTE CoreRANMobile Network FunctionsCloud-NativeKubernetesMVNONetwork SecurityTelco Infrastructure

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-20 · rubric v0.12.0
Composite quality — 1.1/100 · minimal
Contract Quality 0.0 / 21
Developer Ergonomics 1.2 / 17
Access Clarity 0.0 / 17
Operational Transparency 0.0 / 11
Contract Governance 0.0 / 10
Discoverability 3.5 / 9
Regulatory Posture 0.0 / 15
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
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
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Regulatory Posture applies to this provider. Its tags matched the Telecommunications regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/axyomcore: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

Resources

Operate 1

Status, limits, changes, and where to get help

Support
Support

Company 3

The organization behind the API

Website
Website
 About
About
 Blog
Blog

Source (apis.yml)

apis.yml Raw ↑ 
name: AxyomCore
description: 'Telecom infrastructure software vendor, styled Axyom.Core, supplying cloud-native 4G and 5G mobile core and
  RAN network functions (CNFs) that run inside communications service provider networks. Product lines cover 4G core, Femto
  core, security gateway, RAN and full-MVNO deployments, with Red Hat OpenShift support. Part of Lumine Group following a
  carve-out from Casa Systems. NO PUBLIC API SURFACE: the company sells into operator networks through RFP and direct engagement,
  and publishes no developer portal, API documentation, or machine-readable contract. That is an absence of a PUBLIC interface,
  not an absence of APIs — mobile core network functions are API-driven by construction, but those interfaces reach customers
  under operator contracts rather than a public developer program.'
url: https://raw.githubusercontent.com/api-evangelist/axyomcore/refs/heads/main/apis.yml
created: '2026-08-17'
modified: '2026-08-17'
specificationVersion: '0.23'
tags:
- Telecommunications
- 5G Core
- 4G/LTE Core
- RAN
- Mobile Network Functions
- Cloud-Native
- Kubernetes
- MVNO
- Network Security
- Telco Infrastructure
apis: []
common:
- type: Website
  url: https://axyomcore.ai
- type: About
  url: https://axyomcore.ai/about-us
- type: Support
  url: https://axyomcore.ai/contact-us
- type: Blog
  url: https://axyomcore.ai/en/news-insights
maintainers:
- FN: AxyomCore
  url: https://axyomcore.ai
generated:
  by: apis.io/add
  model: claude-opus-4-8
  confidence: 2
  at: '2026-08-17T16:14:07.521Z'
x-review:
  reviewed: '2026-08-17'
  reviewed_by: Kin Lane
  decision: listed
  note: 'Parked by the intake gate as no_consumable_surface. Listed anyway on the standing rule that a valid company on a
    domain it owns gets a listing and a low score, because the score is what gives a vendor something to improve against.
    Roughly half the catalog carries no apis[] entry. Verified 2026-08-17: axyomcore.ai and axyomcore.com both resolve and
    are owned by the company; the advertised apis.json 404s; developer., docs. and api. subdomains do not resolve; the word
    "api" appears zero times on the homepage; the site is HubSpot-built with a Submit RFP call to action. No contract was
    invented to fill the gap.'