NetBox Labs
NetBox Labs is the commercial company behind NetBox, the open-source network source-of-truth (DCIM and IPAM) used by network and infrastructure teams to model sites, racks, devices, interfaces, IP addresses, prefixes, VLANs, circuits, VPNs, and tenancy. It offers NetBox Cloud and NetBox Enterprise alongside the OSS project. NetBox exposes a comprehensive token-authenticated REST API (OpenAPI 3.0, 1,000+ operations across dcim/ipam/circuits/tenancy/virtualization/vpn/wireless), a read-only GraphQL API, official Python (pynetbox) and Go (go-netbox) client libraries, and an official read-only Model Context Protocol (MCP) server for AI agents. The platform is SOC 2 Type II compliant.
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 NetBox Labs the way a machine reads it — 18 machine-readable artifacts across 13 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 — NetBox Labs scores 52.2/100 (developing), with a separate agent-readiness read of 34/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 NetBox Labs
Each block below is one kind of artifact we hold for NetBox Labs. 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 13
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.
NetBox Labs authentication-check API
The authentication-check API from NetBox Labs — 1 operation(s) for authentication-check.
NetBox Labs circuits API
The circuits API from NetBox Labs — 24 operation(s) for circuits.
NetBox Labs core API
The core API from NetBox Labs — 21 operation(s) for core.
NetBox Labs dcim API
The dcim API from NetBox Labs — 103 operation(s) for dcim.
NetBox Labs extras API
The extras API from NetBox Labs — 49 operation(s) for extras.
NetBox Labs ipam API
The ipam API from NetBox Labs — 41 operation(s) for ipam.
NetBox Labs schema API
The schema API from NetBox Labs — 1 operation(s) for schema.
NetBox Labs status API
The status API from NetBox Labs — 1 operation(s) for status.
NetBox Labs tenancy API
The tenancy API from NetBox Labs — 12 operation(s) for tenancy.
NetBox Labs users API
The users API from NetBox Labs — 14 operation(s) for users.
NetBox Labs virtualization API
The virtualization API from NetBox Labs — 15 operation(s) for virtualization.
NetBox Labs vpn API
The vpn API from NetBox Labs — 20 operation(s) for vpn.
NetBox Labs wireless API
The wireless API from NetBox Labs — 6 operation(s) for wireless.
Scroll within the panel for all 13 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
netbox-labs-mcp.yml
MCP SERVERSecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for NetBox Labs — 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.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/netbox-labs · machine-readable index on apis.io