SNMP
Simple Network Management Protocol (SNMP) is the foundational IETF standard for monitoring and managing network devices. SNMP defines a request/response protocol over UDP (ports 161 and 162) for retrieving and altering management variables exposed by agents on routers, switches, servers, UPSs, and other equipment, plus an asynchronous trap/notification channel for event delivery. The protocol family spans three major generations — SNMPv1 (RFC 1157), SNMPv2c (RFC 1901-1908), and the modular SNMPv3 architecture (RFC 3411-3418, extended by RFC 7860 for HMAC-SHA-2 authentication) — and is paired with the Structure of Management Information (SMI) and a vast catalog of MIB modules, most notably the IF-MIB (RFC 2863) for network interfaces. SNMP remains the lingua franca of network monitoring, consumed primarily by NMS platforms such as Nagios, Zabbix, PRTG, SolarWinds, LibreNMS, and Observium, and implemented in open source primarily by the Net-SNMP suite.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles SNMP the way a machine reads it — 7 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 — SNMP scores 14.3/100 (minimal), with a separate agent-readiness read of 0/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 SNMP
Each block below is one kind of artifact we hold for SNMP. 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.
SNMPv1 (RFC 1157)
The original Simple Network Management Protocol defined in RFC 1157 (May 1990). Establishes the five core PDUs (GetRequest, GetNextRequest, GetResponse, SetRequest, Trap), commu...
SNMPv2c (RFC 1901-1908)
Community-based SNMPv2, the most widely deployed version of SNMP in production today. Adds the GetBulkRequest PDU for efficient table retrieval and the InformRequest PDU for ack...
SNMPv3 Architecture (RFC 3411-3418)
The modular SNMPv3 management framework. RFC 3411 defines the SNMP engine, Message Processing Subsystem, Security Subsystem, and Access Control Subsystem; RFC 3414 specifies the...
IF-MIB (RFC 2863) — The Interfaces Group MIB
The canonical SNMP MIB module for network interface management, published June 2000. Defines ifTable, ifXTable, ifStackTable, and ifRcvAddressTable, plus the ifType enumeration ...
SMI and the OID Tree
Structure of Management Information — the data definition language and naming scheme that every MIB module is written against. The IANA SMI Numbers registry administers the OID ...
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.
Snmp Context
JSON-LDSecurity Posture 1
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 SNMP — 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
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/snmp · machine-readable index on apis.io