Cisco Nexus Dashboard
APIs for managing and monitoring Cisco Nexus data center switches and network infrastructure.
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 Cisco Nexus Dashboard the way a machine reads it — 165 machine-readable artifacts across 16 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 — Cisco Nexus Dashboard scores 54.3/100 (developing), with a separate agent-readiness read of 55/100 (agent ready). 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 Cisco Nexus Dashboard
Each block below is one kind of artifact we hold for Cisco Nexus Dashboard. 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 16
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.
Cisco NX-API CLI
API that accepts show commands and configuration commands in CLI format.
Cisco Nexus Dashboard REST API
Unified API for Nexus Dashboard Insights, Orchestrator, and Fabric Controller.
Cisco Nexus Dashboard Fabric Controller API
REST API for managing and automating Nexus and MDS fabrics including LAN, SAN, and IP Fabric for Media deployments.
Cisco Nexus Dashboard Orchestrator API
API for multi-site orchestration of ACI, Cloud ACI, and DCNM fabrics with policy management and segmentation.
Cisco Nexus Dashboard Insights API
API for network analytics, telemetry, anomaly detection, and troubleshooting across data center fabrics.
Cisco DCNM REST API
Data Center Network Manager API for managing Nexus fabric deployments.
Cisco NETCONF/YANG API
Model-driven API using YANG data models for Nexus devices.
Cisco NX-OS RESTCONF API
HTTP-based protocol for configuring YANG-defined data on Nexus switches supporting XML and JSON payload encodings.
Cisco NX-OS gNMI/gRPC API
gRPC Network Management Interface for streaming telemetry and configuration management on Nexus switches.
Cisco NX-OS Model-Driven Telemetry API
Streaming telemetry interface for real-time operational data collection from Nexus switches using YANG models.
Cisco NX-OS Python SDK API
Python Software Development Kit for programmatic access to Nexus 9000 Series switch modules including interfaces, VLANs, ACLs, and routes.
Cisco Nexus Dashboard Authentication API
Session authentication and token management via aaaLogin and aaaLogout
Cisco Nexus Dashboard Interfaces API
Physical interface configuration and operational state using the l1PhysIf managed object class (DN sys/intf/phys-[id])
Cisco Nexus Dashboard Routing API
IPv4 and IPv6 static route configuration using ipv4Route/ipv6Route managed objects and BGP protocol management using bgpEntity hierarchy
Cisco Nexus Dashboard System API
Top-level system information and feature management via topSystem and fmEntity managed objects
Cisco Nexus Dashboard VLANs API
VLAN bridge domain management using the l2BD managed object class (DN sys/bd/bd-[vlan-id]) and SVI interface configuration using sviIf
Scroll within the panel for all 16 ·
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).
Cisco NX-API REST
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.
Cisco Nexus 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.
Cisco Nexus Finops
FINOPSFeatures 8
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.
DME Object Model REST API
RESTful access to the NX-OS Data Management Engine object model for switch configuration and operational state through managed objects.
VLAN and SVI Management
Create, modify, and delete VLAN bridge domains and Switch Virtual Interfaces for Layer 2 and Layer 3 networking.
Interface Configuration
Programmatically configure physical Ethernet interfaces including speed, duplex, MTU, switchport mode, and VLAN assignment.
BGP Routing Management
Configure and monitor BGP routing protocol including neighbors, route policies, and address families.
Static Route Management
Create and manage IPv4 static routes across VRFs with next-hop specifications and route preferences.
Feature Management
Enable and disable NX-OS features programmatically including interface-vlan, BGP, OSPF, and LACP.
Streaming Telemetry
Real-time operational data collection using gNMI/gRPC and model-driven telemetry with YANG models.
Multi-Site Orchestration
Unified policy management and orchestration across multiple ACI, Cloud ACI, and DCNM fabrics.
Scroll within the panel for all 8 ·
Semantic Vocabularies 2
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.
Cisco Nexus 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.
Cisco Nexus Dashboard API Rules
SPECTRALCisco Nexus Dashboard API Rules
SPECTRALJSON Schema 57
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.
AaaLoginResponse
JSON SCHEMABdEntityPayload
JSON SCHEMABgpDom
JSON SCHEMABgpEntity
JSON SCHEMABgpEntityResponse
JSON SCHEMABgpInst
JSON SCHEMABgpPeer
JSON SCHEMAErrorResponse
JSON SCHEMAFmEntityPayload
JSON SCHEMAImDataResponse
JSON SCHEMACisco Nexus NX-API REST Interface Schema
JSON SCHEMAInterfaceEntityPayload
JSON SCHEMAIpv4InstPayload
JSON SCHEMAIpv4Nexthop
JSON SCHEMAIpv4Route
JSON SCHEMAIpv4RouteListResponse
JSON SCHEMAIpv4RouteResponse
JSON SCHEMAL1PhysIf
JSON SCHEMAL2BD
JSON SCHEMAAaaLoginResponse
JSON SCHEMABdEntityPayload
JSON SCHEMABgpDom
JSON SCHEMABgpEntityResponse
JSON SCHEMABgpEntity
JSON SCHEMABgpInst
JSON SCHEMABgpPeer
JSON SCHEMAErrorResponse
JSON SCHEMAFmEntityPayload
JSON SCHEMAImDataResponse
JSON SCHEMAInterfaceEntityPayload
JSON SCHEMAIpv4InstPayload
JSON SCHEMAIpv4Nexthop
JSON SCHEMAIpv4RouteListResponse
JSON SCHEMAIpv4RouteResponse
JSON SCHEMAIpv4Route
JSON SCHEMAL1PhysIf
JSON SCHEMAL2BD
JSON SCHEMAPhysicalInterfaceListResponse
JSON SCHEMAPhysicalInterfaceResponse
JSON SCHEMASviIfPayload
JSON SCHEMASviIf
JSON SCHEMASviInterfaceResponse
JSON SCHEMATopSystemPayload
JSON SCHEMATopSystemResponse
JSON SCHEMATopSystem
JSON SCHEMAVlanBridgeDomainListResponse
JSON SCHEMAVlanBridgeDomainResponse
JSON SCHEMAPhysicalInterfaceListResponse
JSON SCHEMAPhysicalInterfaceResponse
JSON SCHEMASviIf
JSON SCHEMASviIfPayload
JSON SCHEMASviInterfaceResponse
JSON SCHEMATopSystem
JSON SCHEMATopSystemPayload
JSON SCHEMATopSystemResponse
JSON SCHEMAVlanBridgeDomainListResponse
JSON SCHEMAVlanBridgeDomainResponse
JSON SCHEMAScroll within the panel for all 57 ·
JSON Structure 29
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.
Cisco Nexus Nxapi Rest Aaa Login Response Structure
JSON STRUCTURECisco Nexus Nxapi Rest Bd Entity Payload Structure
JSON STRUCTURECisco Nexus Nxapi Rest Bgp Dom Structure
JSON STRUCTURECisco Nexus Nxapi Rest Bgp Entity Response Structure
JSON STRUCTURECisco Nexus Nxapi Rest Bgp Entity Structure
JSON STRUCTURECisco Nexus Nxapi Rest Bgp Inst Structure
JSON STRUCTURECisco Nexus Nxapi Rest Bgp Peer Structure
JSON STRUCTURECisco Nexus Nxapi Rest Error Response Structure
JSON STRUCTURECisco Nexus Nxapi Rest Fm Entity Payload Structure
JSON STRUCTURECisco Nexus Nxapi Rest Im Data Response Structure
JSON STRUCTURECisco Nexus Nxapi Rest Ipv4 Inst Payload Structure
JSON STRUCTURECisco Nexus Nxapi Rest Ipv4 Nexthop Structure
JSON STRUCTURECisco Nexus Nxapi Rest Ipv4 Route Response Structure
JSON STRUCTURECisco Nexus Nxapi Rest Ipv4 Route Structure
JSON STRUCTURECisco Nexus Nxapi Rest L1 Phys If Structure
JSON STRUCTURECisco Nexus Nxapi Rest L2 Bd Structure
JSON STRUCTURECisco Nexus Nxapi Rest Svi If Payload Structure
JSON STRUCTURECisco Nexus Nxapi Rest Svi If Structure
JSON STRUCTURECisco Nexus Nxapi Rest Svi Interface Response Structure
JSON STRUCTURECisco Nexus Nxapi Rest Top System Payload Structure
JSON STRUCTURECisco Nexus Nxapi Rest Top System Response Structure
JSON STRUCTURECisco Nexus Nxapi Rest Top System Structure
JSON STRUCTURECisco Nexus Structure
JSON STRUCTUREScroll within the panel for all 29 ·
Examples 34
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.
Scroll within the panel for all 34 ·
Security 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.
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 5
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.
Data Center Network Automation
Automate switch configuration, VLAN provisioning, and routing changes across large-scale data center fabrics.
Network Monitoring and Analytics
Collect real-time telemetry data from Nexus switches for performance monitoring, anomaly detection, and capacity planning.
Multi-Site Fabric Management
Orchestrate network policies and connectivity across geographically distributed data center fabrics.
Infrastructure as Code
Define and manage network infrastructure configurations using YANG models, NETCONF, and RESTCONF for version-controlled deployments.
Compliance and Auditing
Programmatically verify switch configurations against security baselines and generate compliance reports.
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Ansible
Automate Nexus switch configuration using Ansible NX-OS modules and playbooks for declarative network management.
Terraform
Provision and manage Cisco ACI and Nexus infrastructure using the Terraform Cisco provider.
Cisco ACI
Application Centric Infrastructure integration for policy-driven network automation with Nexus 9000 switches.
Splunk
Forward NX-OS streaming telemetry and syslog data to Splunk for network analytics and SIEM integration.
ServiceNow
Integrate Nexus Dashboard events and alerts with ServiceNow ITSM for automated incident management.
Resources
Every other property we hold for Cisco Nexus Dashboard — 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 2
Portal, sign-up, and the first successful call
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/cisco-nexus · machine-readable index on apis.io