MEF NRP API

Name: MEF NRP API
Brand: MEF NRP API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring Observabilitynone10 EndpointsREST

For Agents

Provision and inspect MEF Network Resource Provisioning forwarding constructs and logical termination points so an agent can automate carrier-grade network connectivity changes.

Install Jentic One Beta

Connect the MEF NRP API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MEF NRP API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with MEF NRP API.

List ForwardingConstructs across the carrier network

Filter ForwardingConstructs by lifecycle state to find pending or active services

Retrieve a specific ForwardingConstruct by id including its endpoints and constraints

GET STARTED

Start building with MEF NRP API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for MEF NRP API, keeping it validated and agent-ready. The MEF Network Resource Provisioning API is a standards-based interface defined by the MEF Forum for managing network connectivity at the carrier-network layer. The 10 endpoints model two core resources — ForwardingConstruct and LogicalTerminationPoint — supporting create, read, update, delete, and state-based queries. It is used by carriers and large enterprises to programmatically provision and inspect MEF-aligned network services.

Use Cases

Patterns agents use MEF NRP API for, with concrete tasks.

★ Automated Network Service Provisioning

Carrier operations teams use the MEF NRP API to provision Ethernet services across a multi-domain network without writing per-vendor element-manager scripts. A single POST or PUT against ForwardingConstruct creates the end-to-end service and returns the resulting object for verification. This compresses multi-day manual provisioning into a single transaction with a uniform contract.

Create a ForwardingConstruct connecting LogicalTerminationPoints uniID=A and uniID=B with a 1Gbps capacity and admin state=ACTIVE.

Network Inventory Reconciliation

Reconcile an inventory database with the live MEF NRP view by listing ForwardingConstructs and LogicalTerminationPoints and diffing fields such as capacity, admin state, and endpoint references. Operations and finance teams use this nightly to catch services that drifted from the order-of-record. It eliminates the manual element-manager export step that legacy operations workflows usually require.

List all ForwardingConstructs and emit a diff of admin_state and capacity against the inventory snapshot from yesterday.

Service-State Monitoring and Alerting

Run a scheduled query against ForwardingConstruct/findByState to catch services stuck in pending or fault states and alert the on-call NOC. Because state filtering is a first-class endpoint, the operations agent can run cheap polls without iterating the full inventory. NOC teams use this to drive a paging policy that reflects the actual MEF service model.

Call /ForwardingConstruct/findByState with state=PENDING every five minutes and page the NOC if the count is greater than zero for more than 30 minutes.

Agent-Driven Capacity Adjustment

When a customer requests a capacity bump, an agent can validate the existing ForwardingConstruct, raise the bandwidth, and confirm the change all through MEF NRP. With Jentic the agent searches by intent, loads the schema for the update operation, and executes it inside a guarded workflow. This turns a ticket-driven carrier change into an autonomous one without touching vendor element managers.

Retrieve ForwardingConstruct id=fc-7841, increase its capacity from 1Gbps to 5Gbps via the update operation, and confirm the returned admin_state is ACTIVE.

Key Endpoints

10 endpoints — jentic publishes the only available openapi specification for mef nrp api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/ForwardingConstruct

List ForwardingConstructs

GET

/ForwardingConstruct/findByState

List ForwardingConstructs filtered by lifecycle state

GET

/ForwardingConstruct/{id}

Retrieve a single ForwardingConstruct

PUT

/ForwardingConstruct/{id}

Update a ForwardingConstruct

GET

/LogicalTerminationPoint

List LogicalTerminationPoints

GET

/LogicalTerminationPoint/{uniID}

Retrieve a LogicalTerminationPoint by UNI id

GET

/ForwardingConstruct

List ForwardingConstructs

GET

/ForwardingConstruct/findByState

List ForwardingConstructs filtered by lifecycle state

GET

/ForwardingConstruct/{id}

Retrieve a single ForwardingConstruct

PUT

/ForwardingConstruct/{id}

Update a ForwardingConstruct

GET

/LogicalTerminationPoint

List LogicalTerminationPoints

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

MEF NRP deployments typically use TLS client certificates or bearer tokens issued by the carrier. Jentic stores the relevant credentials encrypted in the vault per environment so the agent never holds the operator's secrets.

Intent-based discovery

Agents search by intent (e.g. 'list MEF forwarding constructs in pending state') and Jentic returns the matching MEF NRP operation with the exact path and parameter schema, including the state filter on findByState.

Time to first call

Direct MEF NRP integration: 3-5 days for spec interpretation, carrier-specific auth, and idempotent retry logic. Through Jentic: 1-2 hours — search, load schema, execute against the carrier endpoint.

FAQs

Specific to using MEF NRP API through Jentic.

Why is there no official OpenAPI spec for MEF NRP API?

MEF Forum publishes the NRP standard as YANG models and reference documents rather than as a maintained OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call MEF NRP API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the MEF NRP API use?

The reference spec does not declare a security scheme — auth is provided by the carrier deploying the API, typically TLS client certificates or bearer tokens issued by the operator. When you call it through Jentic, the operator-specific credentials are stored encrypted in the vault and injected at execution time.

Can I list ForwardingConstructs by state?

Yes. The /ForwardingConstruct/findByState endpoint accepts a state parameter and returns the constructs matching that lifecycle state, which is more efficient than listing all and filtering client-side.

What are the rate limits for the MEF NRP API?

Rate limits depend on the carrier deployment — the MEF reference spec does not define numerical limits. Treat write operations against /ForwardingConstruct conservatively and back off on 429 or 503 responses before retrying through Jentic.

How do I update a ForwardingConstruct through Jentic?

Search Jentic for update an MEF ForwardingConstruct, load the schema for the PUT on /ForwardingConstruct/{id}, and execute with the id and changed fields such as capacity or admin_state. Jentic returns the updated object so the agent can verify the change.

Is the MEF NRP API a public API?

No — MEF NRP is implemented by individual carriers and exposed only to that carrier's customers and operations teams. The OpenAPI spec describes the standard contract; the actual base URL and credentials come from the carrier deploying it.

MEF NRP API

Connect the MEF NRP API to your agent

Capabilities

Start building with MEF NRP API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs