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 13 more developer resources.

26.6/100 thin ▬ flat Agent 3/100 human only self hosted · Apache-2.0 Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
AccessFreemium
2 APIs
Cloud-NativeContainersIncubatingKubernetesNetworkingPlugins

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Open Source Surface applies to this provider. This product is open source and we read its repository directly, so Open Source Surface carries 10 points of the composite. It is scored from what the repository actually publishes — a security policy, a contribution guide, a release history, a code of conduct — read live from the provider rather than inferred from our own catalog pointers. This facet adds; nothing was taken away to make room for it. An open-source project is not excused from the commercial facets, because exemption would strip it of the points it does earn. If we have the wrong repository, or this product is not open source, say so on your provider repo and we will drop the facet rather than have you publish against it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 90 points between them, because the conditional facet above carries the other 10. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 90% 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/. 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 github.com/api-evangelist/cni: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

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 4

Reference material describing how the API behaves

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Build 4

SDKs, sample code, and the tooling you integrate with

Access & Security 1

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 1

Pricing, plans, and the legal terms of use

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
deliveryModel:
  model: self-hosted
  license: Apache-2.0
  open_source: true
  commercial: false
  callable_host: false
  label: Self-hosted open source · you run it yourself
  confidence: high
  source:
  - license
  generated: '2026-08-28'
  method: derived
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
tags_raw:
- Cloud Native
- Containers
- Incubating
- Kubernetes
- Networking
- Plugins
created: '2026-03-16'
modified: '2026-04-23'
specificationVersion: '0.23'
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: IssueTracker
  url: https://github.com/containernetworking/cni/issues
- type: Releases
  url: https://github.com/containernetworking/cni/releases
- type: CodeOfConduct
  url: https://github.com/containernetworking/cni/blob/main/CODE-OF-CONDUCT.md
- type: ContributionGuide
  url: https://github.com/containernetworking/cni/blob/main/CONTRIBUTING.md
- type: License
  name: Apache-2.0
  url: https://github.com/containernetworking/cni/blob/main/LICENSE
- 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

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/cni"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/cni/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/cni/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

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.

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