Container Network Interface (CNI) website screenshot

Container Network Interface (CNI)

CNI (Container Network Interface) is a CNCF-incubating project that defines a specification and libraries for configuring network interfaces in Linux containers. It provides a simple exec/stdin interface between the container runtime and network implementation plugins, enabling pluggable networking for Kubernetes and other container orchestrators. The CNI spec defines four operations (ADD, DEL, CHECK, VERSION), a network configuration document format, and a plugin Result document. CNI also publishes a collection of reference plugins (bridge, ipvlan, macvlan, host-device, ptp, loopback) and meta-plugins (portmap, bandwidth, firewall, sbr).

Container Network Interface (CNI) publishes 2 APIs on the APIs.io network. Tagged areas include Cloud Native, Containers, Incubating, Kubernetes, and Networking.

The Container Network Interface (CNI) catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

Container Network Interface (CNI)’s developer surface includes documentation and 8 more developer resources.

35.3/100 thin ▬ flat Agent 3/100 human only Full breakdown ↓
scored 2026-07-28 · rubric v0.6
AccessFreemium
2 APIs
Cloud NativeContainersIncubatingKubernetesNetworkingPlugins

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-28 · rubric v0.6
Composite quality — 35.3/100 · thin
Contract Quality 7.3 / 25
Developer Ergonomics 1.7 / 20
Commercial Clarity 7.9 / 20
Operational Transparency 4.8 / 13
Governance 7.0 / 12
Discoverability 6.7 / 10
Agent readiness — 3/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
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 7 / 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
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/cni: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 2

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

CNI Specification

The CNI specification defines the interface between container runtimes and network plugins. It specifies how runtimes invoke plugins via environment variables (CNI_COMMAND, CNI_...

CNI Reference Plugins

A collection of reference and example networking plugins maintained by the containernetworking team that implement the CNI specification. Includes main plugins such as bridge, i...

Pricing Plans 1

Published pricing tiers and plan structures.

Cni Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Cni Rate Limits

5 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Cni Finops

FINOPS

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Cni Context

0 classes · 11 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Container Network Interface (CNI) API Rules

6 rules · 4 warnings 2 info

SPECTRAL

JSON Schema 2

Standalone JSON Schema definitions for this provider's data models.

CNI Network Configuration

11 properties

JSON SCHEMA

CNI Plugin Result

5 properties

JSON SCHEMA

Security Posture 1

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

Cni Domain Security

TLSv1.3 · HSTS

SECURITY

Resources

Documentation 3

Reference material describing how the API behaves

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 1

Authentication, authorization, and security posture

Company 1

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: cni
name: Container Network Interface (CNI)
kind: opensource
description: CNI (Container Network Interface) is a CNCF-incubating project that defines a specification and libraries for
  configuring network interfaces in Linux containers. It provides a simple exec/stdin interface between the container runtime
  and network implementation plugins, enabling pluggable networking for Kubernetes and other container orchestrators. The
  CNI spec defines four operations (ADD, DEL, CHECK, VERSION), a network configuration document format, and a plugin Result
  document. CNI also publishes a collection of reference plugins (bridge, ipvlan, macvlan, host-device, ptp, loopback) and
  meta-plugins (portmap, bandwidth, firewall, sbr).
url: https://www.cni.dev
accessModel:
  pricing: freemium
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Freemium
  confidence: medium
  source:
  - plans
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/cni.png
tags:
- Cloud Native
- Containers
- Incubating
- Kubernetes
- Networking
- Plugins
created: '2026-03-16'
modified: '2026-04-23'
specificationVersion: '0.19'
type: Index
apis:
- aid: cni:cni-spec
  name: CNI Specification
  description: The CNI specification defines the interface between container runtimes and network plugins. It specifies how
    runtimes invoke plugins via environment variables (CNI_COMMAND, CNI_CONTAINERID, CNI_NETNS, CNI_IFNAME, CNI_PATH, CNI_ARGS)
    and stdin configuration, and how plugins respond on stdout with network interface details. The spec covers ADD, DEL, CHECK,
    and VERSION operations for managing container network attachments, and defines the plugin chaining model used by meta-plugins.
  humanURL: https://www.cni.dev/docs/spec/
  properties:
  - type: Documentation
    url: https://www.cni.dev/docs/spec/
  - type: GitHubRepository
    url: https://github.com/containernetworking/cni
  - type: JSONSchema
    url: json-schema/cni-network-config-schema.json
  - type: JSONSchema
    url: json-schema/cni-result-schema.json
  - type: JSONLDContext
    url: json-ld/cni-context.jsonld
  tags:
  - Network Plugins
  - Specification
  x-features:
  - name: ADD operation
    description: Attach a container to a network and return a Result document with assigned interfaces, IPs, routes, and DNS.
  - name: DEL operation
    description: Detach a container from a network and tear down allocated resources.
  - name: CHECK operation
    description: Verify the container's current attachment matches the prior ADD result.
  - name: VERSION operation
    description: Report the CNI spec versions a plugin supports.
  - name: Plugin Chaining
    description: Meta-plugin chaining model where a chain shares previous Result via prevResult.
  - name: Network Config Schema
    description: Schema for the JSON document that describes a network and its plugin chain.
  - name: Result Schema
    description: Schema for the Result document that plugins emit on stdout.
  x-useCases:
  - name: Kubernetes CNI Plugin
    description: Implement a CNI plugin that integrates with Kubernetes / containerd / CRI-O.
  - name: Network Validation
    description: Validate network configurations and plugin Result documents against the spec.
  - name: Custom SDN
    description: Build custom software-defined networks for containers using a portable plugin contract.
- aid: cni:cni-plugins
  name: CNI Reference Plugins
  description: A collection of reference and example networking plugins maintained by the containernetworking team that implement
    the CNI specification. Includes main plugins such as bridge, ipvlan, macvlan, ptp, host-device, and loopback, as well
    as meta plugins such as portmap, bandwidth, firewall, sbr, and tuning for additional networking functionality.
  humanURL: https://www.cni.dev/plugins/current/
  properties:
  - type: Documentation
    url: https://www.cni.dev/plugins/current/
  - type: GitHubRepository
    url: https://github.com/containernetworking/plugins
  tags:
  - Containers
  - Kubernetes
  - Linux
  - Network Plugins
  - Networking
  x-features:
  - name: bridge
    description: Linux-bridge plugin attaching container veth pairs to a bridge.
  - name: ipvlan
    description: IPVLAN plugin for L2/L3 IPVLAN attachments.
  - name: macvlan
    description: MACVLAN plugin for MACVLAN attachments.
  - name: host-device
    description: Plugin that moves an existing host device into a container netns.
  - name: ptp
    description: Point-to-point veth-pair plugin.
  - name: loopback
    description: Loopback interface configuration.
  - name: portmap
    description: Meta-plugin that publishes container ports to the host via NAT.
  - name: bandwidth
    description: Meta-plugin that applies ingress/egress traffic shaping with tc.
  - name: firewall
    description: Meta-plugin that applies iptables/nftables rules for a container.
  - name: sbr
    description: Source-based routing meta-plugin.
  x-useCases:
  - name: Kubernetes Pod Networking
    description: Use bridge + portmap as a minimal Kubernetes pod networking stack.
  - name: Multi-Network Pods
    description: Combine reference plugins via Multus or chains for multi-NIC pods.
common:
- type: DomainSecurity
  url: security/cni-domain-security.yml
- type: Website
  url: https://www.cni.dev/
- type: Documentation
  url: https://www.cni.dev/docs/
- type: GitHubOrganization
  url: https://github.com/containernetworking
- type: GitHubRepository
  url: https://github.com/containernetworking/cni
- type: GitHubRepository
  url: https://github.com/containernetworking/plugins
- type: JSONLDContext
  url: json-ld/cni-context.jsonld
- type: JSONSchema
  url: json-schema/cni-network-config-schema.json
- type: JSONSchema
  url: json-schema/cni-result-schema.json
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com