NeuVector
NeuVector is an open source, full lifecycle container security platform maintained by SUSE. It provides vulnerability scanning, runtime protection, compliance monitoring, and a Layer 7 container firewall for Kubernetes environments. The NeuVector REST API allows automation of scanning, policy management, configuration, user administration, and federated cluster operations.
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 NeuVector the way a machine reads it — 35 machine-readable artifacts across 31 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 — NeuVector scores 32.6/100 (thin), with a separate agent-readiness read of 24/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 NeuVector
Each block below is one kind of artifact we hold for NeuVector. 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 31
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.
NeuVector Admission API
Admission Control
NeuVector Apikey API
The Apikey API from NeuVector — 2 operation(s) for apikey.
NeuVector Authentication API
Authenticates login or logout
NeuVector Compliance API
Operations about Compliance
NeuVector compliance profile. The payload body is the content of the compliance profile yaml file. API
The compliance profile. The payload body is the content of the compliance profile yaml file. API from NeuVector — 1 operation(s) for compliance profile. the payload body is the ...
NeuVector compliance profile. The payload body is the content of the vulnerability profile yaml file. API
The compliance profile. The payload body is the content of the vulnerability profile yaml file. API from NeuVector — 1 operation(s) for compliance profile. the payload body is t...
NeuVector Container API
Operations about Container
NeuVector Controller API
Operations about Controller
NeuVector DLP API
Operations about DLP
NeuVector Enforcer API
Operations about Enforcer
NeuVector EULA API
End-User License Agreement
NeuVector Federation API
Operations about Federation
NeuVector File API
Operations about File
NeuVector File Monitor API
Operations about File Monitor
NeuVector Group API
Operations about Group
NeuVector Host API
Operations about Host
NeuVector Log API
Operations about Log
NeuVector Namespace API
Operations about Namespace
NeuVector Policy API
Operations about Policy
NeuVector Process API
Operations about Process Profile
NeuVector Remote Export Repository API
The Remote Export Repository API from NeuVector — 1 operation(s) for remote export repository.
NeuVector Remote Repository API
The Remote Repository API from NeuVector — 2 operation(s) for remote repository.
NeuVector Response Rule API
Operations about Response Rule
NeuVector Scan API
Operations about Scan
NeuVector Server API
Operations about Server
NeuVector Service API
Operations about Service
NeuVector Sniffer API
Operations about Sniffer
NeuVector System API
Operations about System
NeuVector User API
Operations about User
NeuVector Vulnerability API
Operations about Vulnerability management
NeuVector WAF Rule API
Operations about waf Rule
Scroll within the panel for all 31 ·
Pricing 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.
Neuvector 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.
Neuvector Finops
FINOPSSecurity 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 NeuVector — 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.
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 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/neuvector · machine-readable index on apis.io