ETSI GS MEC 010-2 - Part 2: Application lifecycle, rules and requirements management

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureContainer Orchestrationnone16 EndpointsREST

Connect the ETSI GS MEC 010-2 - Part 2: Application lifecycle, rules and requirements management to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ETSI GS MEC 010-2 - Part 2: Application lifecycle, rules and requirements management, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

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

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 ETSI GS MEC 010-2 - Part 2: Application lifecycle, rules and requirements management API.

Onboard a new MEC application package by uploading the application descriptor to the MEO

Query onboarded application packages with filters by application descriptor ID or operational state

Read the AppD content of an individual application package for inspection or auditing

GET STARTED

Start building with ETSI GS MEC 010-2 - Part 2: Application lifecycle, rules and requirements management API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for ETSI GS MEC 010-2 - Part 2: Application lifecycle, rules and requirements management, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for ETSI GS MEC 010-2 - Part 2: Application lifecycle, rules and requirements management, keeping it validated and agent-ready. The ETSI MEC 010-2 specification defines the standard interface used by Multi-access Edge Computing orchestrators to onboard, manage and lifecycle application packages at the network edge. It exposes operations for uploading application descriptors, querying onboarded packages, and subscribing to lifecycle notifications, enabling MEO and MEPM components to interoperate across vendors. The interface is reference-only and uses a localhost base URL that operators replace with their MEO endpoint.

Use Cases

Patterns agents use ETSI GS MEC 010-2 - Part 2: Application lifecycle, rules and requirements management API for, with concrete tasks.

★ Edge application onboarding pipeline

An orchestration controller pushes a vendor-supplied application package to a MEO so it becomes available for instantiation at the edge. POST /app_packages accepts the package metadata and returns an appPkgId that the controller uses to track lifecycle state. This is the standard ETSI flow that decouples orchestrators from MEC platform implementations.

POST /app_packages with the application descriptor reference, then poll GET /app_packages/{appPkgId} until the operational state is ENABLED.

Multi-vendor MEO inventory

A network operator inventories every application package onboarded across MEO instances from different vendors using the standard ETSI MEC 010-2 query interface. GET /app_packages returns a normalised list that the operator can compare against expected packages for compliance reporting.

GET /app_packages and aggregate the response into a CSV grouped by appDId, including operational state and onboarding timestamp.

Lifecycle event subscriptions

An OSS/BSS system subscribes to package lifecycle events so it can react to onboarding completion or operational state changes without polling. POST /subscriptions registers a subscription with a callback URI, and the MEO POSTs notifications to the configured endpoint via /user_defined_notification.

POST /subscriptions with the callback URI and filter by appDId, then verify the subscriptionId is returned.

Agent-driven edge package management via Jentic

An AI agent receives a directive to retire a deprecated edge application across all sites. The agent uses Jentic to discover the ETSI MEC 010-2 PATCH operation, sets the operational state to DISABLED on each appPkgId, and confirms the change. Because the spec is published by Jentic, the agent has consistent tool definitions across vendor MEOs.

Search Jentic for 'disable a MEC application package', load the schema for PATCH /app_packages/{appPkgId}, and execute against each target appPkgId.

Key Endpoints

16 endpoints — jentic publishes the only available openapi specification for etsi gs mec 010-2 - part 2: application lifecycle, rules and requirements management, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/app_packages

Query onboarded application packages

POST

/app_packages

Onboard a new application package

GET

/app_packages/{appPkgId}

Read an individual application package

PATCH

/app_packages/{appPkgId}

Update the operational state of a package

DELETE

/app_packages/{appPkgId}

Delete an application package

POST

/subscriptions

Subscribe to package lifecycle notifications

GET

/app_packages/{appPkgId}/appd

Read the AppD content of a package

GET

/app_packages

Query onboarded application packages

POST

/app_packages

Onboard a new application package

GET

/app_packages/{appPkgId}

Read an individual application package

PATCH

/app_packages/{appPkgId}

Update the operational state of a package

DELETE

/app_packages/{appPkgId}

Delete an application package

Why though Jentic?

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

Credential isolation

Because the ETSI MEC 010-2 spec declares no securitySchemes, operators add their own auth (mTLS or bearer) in front of the MEO. Jentic stores those operator-supplied credentials in the MAXsystem vault and injects them at execution time so the agent never sees raw certificates or tokens.

Intent-based discovery

Agents search by intent such as 'onboard a MEC application package' and Jentic returns the matching ETSI operation with its AppD-aware input schema, so the agent calls the right endpoint without parsing the ETSI normative document.

Time to first call

Direct ETSI MEC 010-2 integration: 1-3 weeks to translate the normative document into working client code. Through Jentic: under an hour to make the first call against a MEO endpoint.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Kubernetes API

Kubernetes orchestrates the containers that often back MEC application packages

Use alongside MEC 010-2 when the agent needs to inspect the underlying pods that an onboarded package runs as

Complementary

OpenStack API

OpenStack provides the NFVI on which many MEC platforms run their VM-based packages

Use alongside MEC 010-2 when the agent needs to verify the VM-based MEPM/MEO infrastructure state

Complementary

Docker Engine API

Docker Engine manages the container images referenced by MEC application descriptors

Use alongside MEC 010-2 when the agent needs to push or inspect images that the AppD references

FAQs

Specific to using ETSI GS MEC 010-2 - Part 2: Application lifecycle, rules and requirements management API through Jentic.

Why is there no official OpenAPI spec for ETSI GS MEC 010-2 Part 2?

ETSI publishes the specification as a printable document and a YAML on its forge, but there is no widely distributed OpenAPI artefact ready for tooling. Jentic generates and maintains this spec so that AI agents and developers can call ETSI MEC 010-2 via structured tooling. It is validated against the published normative interface and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the ETSI MEC 010-2 App Pkg Mgmt API use?

The normative interface does not mandate a specific auth scheme - operators typically front the MEO with mutual TLS or OAuth 2.0 in production, but the spec itself declares no securitySchemes. Through Jentic the credentials configured for your MEO endpoint are kept in the MAXsystem vault.

Can I onboard application packages with this API?

Yes. POST /app_packages creates an application package resource on the MEO, returning the appPkgId used by every subsequent lifecycle operation. The package itself is referenced via the AppD content read through GET /app_packages/{appPkgId}/appd.

What are the rate limits for the ETSI MEC 010-2 App Pkg Mgmt API?

Rate limits are not part of the ETSI specification. They are determined by the specific MEO implementation in use - check vendor documentation for OpenAirInterface, ONAP, or commercial MEC platforms.

How do I subscribe to package lifecycle events through Jentic?

Use the Jentic search query 'subscribe to MEC application package events', which resolves to POST /subscriptions. Provide the callbackUri and any filter, and Jentic executes the call against your configured MEO endpoint.

Is the base URL https://localhost meant literally?

No. The spec uses https://localhost/app_pkgm/v1 as a placeholder because the URL depends on the operator's MEO deployment. Replace it with the actual MEO management address before calling the API.