Mavenir

Mavenir is a US-headquartered (Richardson, Texas) cloud-native telecom network software vendor that builds the software operators run rather than a network or a developer platform of its own. Its portfolio spans Open RAN and vRAN (MAVair), converged packet core and cloud-native IMS (MAVcore), messaging, fraud and security applications, the Mavenir Digital Enablement (MDE) BSS and converged charging stack (MAVapps), private networks, MEC and an Intelligent IoT Platform (MAVedge). In the telecom value chain Mavenir sits upstream of the carrier — it supplies the Combo NEF/SCEF network-exposure function and the BSS that a mobile operator uses to expose and monetize CAMARA and GSMA Open Gateway network APIs, but it does not expose those APIs to developers itself. Its API posture is accordingly partner-gated and sales-led: there is no developer portal at any developer/docs/api subdomain, no self-serve signup, no sandbox, and no downloadable specification on mavenir.com; the only login-bearing surface, support.mavenir.com, is an ADFS-protected customer support wall. What Mavenir does publish is standards work — it is an active CAMARA participant with eleven named individuals in CAMARA governance, is listed in the CAMARA landscape as a Network Capability Solution Provider, co-maintains the camaraproject/WebRTC sandbox API repository (two of the four CODEOWNERS are Mavenir engineers), contributed its own Bring Your Own Number (BYON) OpenAPI definitions to the CAMARA API Backlog, and holds TM Forum Open API Platinum conformance with 20+ certified Open APIs on the MDE BSS platform. Developers reach Mavenir-powered capability only through a carrier or through a channel partner such as Spry Fox Networks, never directly.

Mavenir publishes 4 API contracts indexed on the APIs.io network, including One To One Call API, Push Token API, RACM API, and 1 more. Tagged areas include Telecommunications, United States, Network Vendor, Network APIs, and CAMARA.

The Mavenir catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

Mavenir’s developer surface includes authentication, support, engineering blog, privacy policy, and 31 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

38.1/100 thin ▬ flat Agent 29/100 agent ready Front door AI 6/6 dominant saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

2 published contracts 2 Agent Skills

Telecommunications United States Network Vendor Network APIs CAMARA Open Gateway BSS OSS TM Forum Open RAN 5GIMSMessagingNetwork Exposure FunctionStandards

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 38.1/100 · thin

Contract Quality 10.0 / 19

Developer Ergonomics 4.9 / 15

Access Clarity 4.3 / 15

Operational Transparency 1.0 / 10

Contract Governance 2.9 / 9

Discoverability 4.9 / 8

Regulatory Posture 4.5 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 29/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

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.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/mavenir/"><img src="https://apis.io/badge/mavenir/card.svg" alt="Mavenir on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
Protected Resource Metadata +5 pts — a served /.well-known/oauth-protected-resource carrying `resource` (documented), and naming its authorization_servers (verified)

4 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 28.9 — up to +14.2 composite points
Developer Ergonomics scores 32.7 — up to +13.5 composite points
Contract Quality scores 53.4 — up to +11.7 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/mavenir/apis.yml: open an issue on github.com/api-evangelist/mavenir to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Red Hat Certified Ecosystem (certified partner containers + certified OpenShift operators)	standard	38.3 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

CAMARA

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

OpenAPI

measured — observed by APIs.io (published)

APIs 4

Individual APIs this provider publishes, each with its own machine-readable definition.

Mavenir Digital Enablement (MDE) TM Forum Open APIs

The TM Forum Open APIs implemented in Mavenir's cloud-native Digital Enablement (MDE) BSS, converged charging and digital marketplace platform. Mavenir holds TM Forum Open API C...

Mavenir One To One Call API

APIs related to 1-1 voice/video call session

Mavenir Push Token API

The Push Token API from Mavenir — 1 operation(s) for push token.

Mavenir RACM API

The RACM API from Mavenir — 2 operation(s) for racm.

Open Collections 2

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Bring Your Own Number (BYON) call handling API (VVOIP Service)

OPEN COLLECTION

Bring Your Own Number (BYON) Registration and Connectivity Management (RACM) Service APIs

OPEN COLLECTION

Arazzo Workflows 1

Multi-step API workflows described with the Arazzo specification.

Place and manage a 1-1 VVoIP call (Mavenir BYON)

Originate a one-to-one voice/video session on a Mavenir BYON call handling deployment, read it back, drive it to Connected, then terminate it. Every operationId is verified agai...

ARAZZO

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

Place and manage a 1-1 VVoIP call (Mavenir BYON)

AGENT SKILL

Register a BYON client and keep it connected (Mavenir RACM)

AGENT SKILL

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Mavenir Byon Events

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Mavenir API Rules

57 rules · 50 errors 1 warnings 6 info

SPECTRAL

OpenAPI Overlays 2

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Mavenir Byon Call Handling Overlay

5 actions · update · mavenir-byon-call-handling-openapi.yml

DERIVED

Mavenir Byon Racm Overlay

7 actions · update · mavenir-byon-racm-openapi.yml

DERIVED

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Mavenir Authentication

http · 1 scheme

SECURITY

Mavenir Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Mavenir Agentic Access

8 operations · 7 acting · 1 human-in-the-loop

8 operations · 7 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

SupportPortal

SupportPortal

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

X-MCPServerCandidate

X-MCPServerCandidate

AgentSkill

AgentSkill

LLMsTxt

LLMsTxt

Design & Contract 8

Pagination, idempotency, versioning, errors, and events

Conventions

Idempotency

ErrorCatalog

Lifecycle

Conformance

DataModel

Webhooks

Arazzo

Scroll for all 8

Build 3

SDKs, sample code, and the tooling you integrate with

Packages

Packages

ToolCrosswalk

ToolCrosswalk

GitHubOrganization

GitHubOrganization

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Compliance

Compliance

Operate 3

Status, limits, changes, and where to get help

PressReleases

PressReleases

Contact

Contact

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

Privacy

Privacy

TermsOfService

TermsOfService

Company 6

The organization behind the API

Website

About

Newsroom

Blog

BlogRSS

LinkedIn

Other 5

Properties that don't map to a standard resource type

Overlay

Overlay

Portfolio

Standards

Standards

Source (apis.yml)

aid: mavenir
url: https://raw.githubusercontent.com/api-evangelist/mavenir/refs/heads/main/apis.yml
x-api-posture: no-product-api
x-api-posture-basis: observed
name: Mavenir
kind: company
description: 'Mavenir is a US-headquartered (Richardson, Texas) cloud-native telecom network software vendor that builds the
  software operators run rather than a network or a developer platform of its own. Its portfolio spans Open RAN and vRAN (MAVair),
  converged packet core and cloud-native IMS (MAVcore), messaging, fraud and security applications, the Mavenir Digital Enablement
  (MDE) BSS and converged charging stack (MAVapps), private networks, MEC and an Intelligent IoT Platform (MAVedge). In the
  telecom value chain Mavenir sits upstream of the carrier — it supplies the Combo NEF/SCEF network-exposure function and
  the BSS that a mobile operator uses to expose and monetize CAMARA and GSMA Open Gateway network APIs, but it does not expose
  those APIs to developers itself. Its API posture is accordingly partner-gated and sales-led: there is no developer portal
  at any developer/docs/api subdomain, no self-serve signup, no sandbox, and no downloadable specification on mavenir.com;
  the only login-bearing surface, support.mavenir.com, is an ADFS-protected customer support wall. What Mavenir does publish
  is standards work — it is an active CAMARA participant with eleven named individuals in CAMARA governance, is listed in
  the CAMARA landscape as a Network Capability Solution Provider, co-maintains the camaraproject/WebRTC sandbox API repository
  (two of the four CODEOWNERS are Mavenir engineers), contributed its own Bring Your Own Number (BYON) OpenAPI definitions
  to the CAMARA API Backlog, and holds TM Forum Open API Platinum conformance with 20+ certified Open APIs on the MDE BSS
  platform. Developers reach Mavenir-powered capability only through a carrier or through a channel partner such as Spry Fox
  Networks, never directly.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  gated_conflict: 'x-api-posture: private but 4 published API entries'
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Telecommunications
- United States
- Network Vendor
- Network APIs
- CAMARA
- Open Gateway
- BSS
- OSS
- TM Forum
- Open RAN
- 5G
- IMS
- Messaging
- Network Exposure Function
- Standards
created: '2026-07-25'
modified: '2026-07-25'
specificationVersion: '0.23'
apis:
- aid: mavenir:mavenir-digital-enablement-tm-forum-open-apis
  name: Mavenir Digital Enablement (MDE) TM Forum Open APIs
  description: 'The TM Forum Open APIs implemented in Mavenir''s cloud-native Digital Enablement (MDE) BSS, converged charging
    and digital marketplace platform. Mavenir holds TM Forum Open API Conformance certification for this product: Silver on
    2022-10-06 covering TMF620 Product Catalog Management, TMF622 Product Ordering, TMF629 Customer Management, TMF632 Party
    Management and TMF667 Document Management, then Platinum on 2023-09-20 with 20+ certified Open APIs. The certification
    is real, published and verifiable through TM Forum, and the interface contracts are TM Forum''s public specifications
    — but Mavenir itself publishes no public API reference, no OpenAPI download and no endpoint for these APIs. They are delivered
    inside a licensed operator deployment and are reachable only under a commercial engagement. The individual 20 certified
    TMF numbers behind the Platinum tier were not itemized in Mavenir''s announcement.'
  humanURL: https://www.mavenir.com/portfolio/mavapps/mavenir-digital-enablement-bss/
  tags:
  - BSS
  - TM Forum
  - Charging
  - Product Catalog
  - Ordering
  properties:
  - type: Documentation
    url: https://www.mavenir.com/portfolio/mavapps/mavenir-digital-enablement-bss/
  - type: Documentation
    url: https://www.mavenir.com/press-releases/mavenir-achieves-platinum-open-api-status-with-landmark-20-open-apis-certified-by-tm-forum/
  - type: Documentation
    url: https://www.mavenir.com/press-releases/mavenirs-cloud-native-business-support-system-suite-achieves-tm-forums-open-api-silver-certification/
- aid: mavenir:mavenir-onetoonecall-api
  name: Mavenir One To One Call API
  description: APIs related to 1-1 voice/video call session
  humanURL: https://github.com/camaraproject/APIBacklog/blob/main/documentation/SupportingDocuments/BYON-CallHandling-Service.yaml
  tags:
  - OneToOneCall
  properties:
  - type: OpenAPI
    url: openapi/mavenir-onetoonecall-api-openapi.yml
  - type: Documentation
    url: https://github.com/camaraproject/WebRTC
  - type: APIReference
    url: https://raw.githubusercontent.com/camaraproject/APIBacklog/main/documentation/SupportingDocuments/BYON-CallHandling-Service.yaml
  - type: APIReference
    url: https://raw.githubusercontent.com/camaraproject/APIBacklog/main/documentation/SupportingDocuments/BYON-RACM-Service.yaml
- aid: mavenir:mavenir-push-token-api
  name: Mavenir Push Token API
  description: The Push Token API from Mavenir — 1 operation(s) for push token.
  humanURL: https://github.com/camaraproject/APIBacklog/blob/main/documentation/SupportingDocuments/BYON-CallHandling-Service.yaml
  tags:
  - Push Token
  properties:
  - type: OpenAPI
    url: openapi/mavenir-push-token-api-openapi.yml
  - type: Documentation
    url: https://github.com/camaraproject/WebRTC
  - type: APIReference
    url: https://raw.githubusercontent.com/camaraproject/APIBacklog/main/documentation/SupportingDocuments/BYON-CallHandling-Service.yaml
  - type: APIReference
    url: https://raw.githubusercontent.com/camaraproject/APIBacklog/main/documentation/SupportingDocuments/BYON-RACM-Service.yaml
- aid: mavenir:mavenir-racm-api
  name: Mavenir RACM API
  description: The RACM API from Mavenir — 2 operation(s) for racm.
  humanURL: https://github.com/camaraproject/APIBacklog/blob/main/documentation/SupportingDocuments/BYON-CallHandling-Service.yaml
  tags:
  - RACM
  properties:
  - type: OpenAPI
    url: openapi/mavenir-racm-api-openapi.yml
  - type: Documentation
    url: https://github.com/camaraproject/WebRTC
  - type: APIReference
    url: https://raw.githubusercontent.com/camaraproject/APIBacklog/main/documentation/SupportingDocuments/BYON-CallHandling-Service.yaml
  - type: APIReference
    url: https://raw.githubusercontent.com/camaraproject/APIBacklog/main/documentation/SupportingDocuments/BYON-RACM-Service.yaml
common:
- type: Overlay
  url: overlays/mavenir-byon-call-handling-overlay.yaml
- type: Overlay
  url: overlays/mavenir-byon-racm-overlay.yaml
- type: DomainSecurity
  url: security/mavenir-domain-security.yml
- type: AgenticAccess
  url: agentic-access/mavenir-agentic-access.yml
- type: Authentication
  url: authentication/mavenir-authentication.yml
- type: Conventions
  url: conventions/mavenir-conventions.yml
- type: Idempotency
  url: conventions/mavenir-conventions.yml
- type: ErrorCatalog
  url: errors/mavenir-problem-types.yml
- type: Lifecycle
  url: lifecycle/mavenir-lifecycle.yml
- type: Conformance
  url: conformance/mavenir-conformance.yml
- type: DataModel
  url: data-model/mavenir-data-model.yml
- type: Webhooks
  url: asyncapi/mavenir-byon-events.yml
- type: Packages
  url: packages/mavenir-packages.yml
- type: X-MCPServerCandidate
  url: mcp/mavenir-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: ToolCrosswalk
  url: mcp/mavenir-tool-crosswalk.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Arazzo
  name: Place and manage a 1-1 VVoIP call (Mavenir BYON)
  url: arazzo/mavenir-byon-place-and-manage-call.yml
- type: LLMsTxt
  url: llms/mavenir-llms.txt
- type: Website
  url: https://www.mavenir.com/
- type: About
  url: https://www.mavenir.com/about/
- type: Portfolio
  url: https://www.mavenir.com/portfolio/mavapps/
- type: Newsroom
  url: https://www.mavenir.com/newsroom/
- type: PressReleases
  url: https://www.mavenir.com/press-releases/
- type: Contact
  url: https://www.mavenir.com/contact-us/
- type: SupportPortal
  url: https://support.mavenir.com/
- type: Support
  url: https://support.mavenir.com/
- type: Blog
  url: https://www.mavenir.com/newsroom/blog/
- type: BlogRSS
  url: https://www.mavenir.com/newsroom/blog/feed/
- type: GitHubOrganization
  url: https://github.com/mavenir
- type: Privacy
  url: https://www.mavenir.com/data-privacy-notice/
- type: TermsOfService
  url: https://www.mavenir.com/terms-use/
- type: Compliance
  url: https://www.mavenir.com/regulatory-compliance/
- type: LinkedIn
  url: https://www.linkedin.com/company/mavenir
- type: Standards
  url: https://github.com/camaraproject/WebRTC
- type: Standards
  url: https://github.com/camaraproject/Governance/blob/main/PARTICIPANTS.MD
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Mavenir API — frequently asked questions

Does Mavenir have an API?

Yes. APIs.io lists 4 APIs from Mavenir, including Mavenir Digital Enablement (MDE) TM Forum Open APIs, Mavenir One To One Call API and Mavenir Push Token API, and 1 more.

Is there an OpenAPI specification for the Mavenir API?

Yes. APIs.io indexes 3 OpenAPI specifications for Mavenir, each linked for download from this page.

How do I authenticate with the Mavenir API?

Mavenir uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Mavenir Authentication.

Is the Mavenir API ready for AI agents?

Mavenir has a Kin Score of 38.1 out of 100 (thin) and an Agent Readiness score of 29.1 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/mavenir"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/mavenir/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/mavenir/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.