Weave Net
Weave Net is an open source container networking plugin that creates a virtual network connecting Docker containers and Kubernetes pods across multiple hosts. It provides automatic IP address management (IPAM), DNS resolution via WeaveDNS, network policy enforcement, and optional encryption for container-to-container communication. The Weave Net daemon exposes a local HTTP API on port 6784 for programmatic network management. Weave Net is maintained by Weaveworks and is archived but remains widely used in production environments.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Weave Net the way a machine reads it — 45 machine-readable artifacts across 5 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Weave Net scores 54.4/100 (developing), with a separate agent-readiness read of 39/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Weave Net
Each block below is one kind of artifact we hold for Weave Net. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 5
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Weave Net DNS API
The DNS API from Weave Net — 2 operation(s) for dns.
Weave Net IPAM API
The IPAM API from Weave Net — 3 operation(s) for ipam.
Weave Net Network API
The Network API from Weave Net — 1 operation(s) for network.
Weave Net Peers API
The Peers API from Weave Net — 2 operation(s) for peers.
Weave Net Status API
The Status API from Weave Net — 1 operation(s) for status.
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Weave Net HTTP API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Weave Net Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Weave Net Finops
FINOPSFeatures 7
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Container Overlay Network
Creates a virtual network connecting containers across multiple hosts without requiring any configuration of the physical network.
Automatic IPAM
Automatically allocates IP addresses to containers from a configurable subnet using distributed consensus.
WeaveDNS
Built-in DNS resolution for containers by hostname, making services discoverable by name on the Weave network.
Network Encryption
Optional encryption of all network traffic using NaCl for secure container-to-container communication.
Kubernetes Integration
Native Kubernetes CNI plugin for pod-to-pod networking across nodes.
Docker Integration
Docker network plugin for seamless multi-host Docker container networking.
Fast Datapath
Kernel-level packet forwarding using Open vSwitch for high-performance networking.
Scroll within the panel for all 7 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Weave Net Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Weave Net API Rules
SPECTRALWeave Net API Rules
SPECTRALJSON Schema 7
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
ConnectRequest
JSON SCHEMAConnectionInfo
JSON SCHEMADNSStatus
JSON SCHEMAIPAMStatus
JSON SCHEMAPeerInfo
JSON SCHEMARouterStatus
JSON SCHEMAStatusResponse
JSON SCHEMAScroll within the panel for all 7 ·
JSON Structure 7
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Weave Net Connect Request Structure
JSON STRUCTUREWeave Net Connection Info Structure
JSON STRUCTUREWeave Net Dns Status Structure
JSON STRUCTUREWeave Net Ipam Status Structure
JSON STRUCTUREWeave Net Peer Info Structure
JSON STRUCTUREWeave Net Router Status Structure
JSON STRUCTUREWeave Net Status Response Structure
JSON STRUCTUREScroll within the panel for all 7 ·
Examples 7
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Weave Net Dns Status Example
EXAMPLEWeave Net Peer Info Example
EXAMPLEScroll within the panel for all 7 ·
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Multi-Host Docker Networking
Connect Docker containers across multiple physical or virtual machines without complex network configuration.
Kubernetes Pod Networking
Provide pod-to-pod networking for Kubernetes clusters as a CNI-compliant network plugin.
Automated IP Management
Automate container IP allocation and release in orchestration workflows.
Service Discovery
Enable container service discovery by DNS name using WeaveDNS.
Resources
Every other property we hold for Weave Net — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 2
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
← All providers · Data indexed from github.com/api-evangelist/weave-net · machine-readable index on apis.io