Netbeez
NetBeez is a network performance monitoring platform that measures the end-user experience across distributed enterprise, remote-worker, and Wi-Fi networks. Hardware and software agents (including Raspberry Pi, Docker, and network-device-hosted agents on Cisco, Extreme, Cumulus, and Nutanix gear) run continuous and ad-hoc tests — ping, HTTP, DNS, traceroute, path analysis, Wi-Fi, and cellular — and report granular one-second-interval metrics to a central dashboard for real-time alerting and historical troubleshooting. The NetBeez API lets dashboard administrators integrate this telemetry with external tools, reporting, and analytics: a JSON-based v2 API documented on Postman at api.netbeez.net supports read and write operations (create targets, run ad-hoc tests), while a deprecated read-only v1 Swagger API is served per-instance. Alerting integrates outbound via webhooks and pre-built connectors for PagerDuty, Slack, Splunk, Microsoft Teams, ServiceNow, SNMP, syslog, and email. NetBeez was surfaced as a portfolio company of Partech.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Netbeez the way a machine reads it — 4 machine-readable artifacts across 1 API, 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 — Netbeez scores 30.2/100 (thin), with a separate agent-readiness read of 6/100 (human only). 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 Netbeez
Each block below is one kind of artifact we hold for Netbeez. 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 1
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.
NetBeez API
Administrator-facing API for integrating NetBeez network-performance telemetry with external tools. v2 is a JSON API (read-write: create targets, run ad-hoc tests) documented on...
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Netbeez Alerts Webhooks
ASYNCAPISecurity Posture 2
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 Netbeez — 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 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Access & Security 1
Authentication, authorization, and security posture
Operate 3
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/netbeez · machine-readable index on apis.io