Netography
Netography Fusion is a SaaS network defense and observability platform (now Vectra Fusion) that ingests cloud VPC flow logs, DNS, and NetFlow/sFlow from AWS, Azure, GCP, IBM, and Oracle to deliver real-time network detection and response without sensors or agents. Its REST API (base https://api.netography.com) exposes analytics and NQL raw-record search, IP/port context labels, threat intelligence lookups, MITRE ATT&CK mapped detection models, response policies and block lists, cloud traffic sources, and context/response integrations. Authentication is a JWT bearer token minted from a NETOSECRET API key. An official MCP server (neto-mcp) exposes the query endpoints to agents.
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 Netography the way a machine reads it — 34 machine-readable artifacts across 28 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 — Netography scores 39.7/100 (thin), with a separate agent-readiness read of 71/100 (agent native). 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.
How we profile Netography
Each block below is one kind of artifact we hold for Netography. 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 28
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.
Netography Analytics API
The Analytics API from Netography — 5 operation(s) for analytics.
Netography API Keys API
The API Keys API from Netography — 3 operation(s) for api keys.
Netography Authentication API
The Authentication API from Netography — 3 operation(s) for authentication.
Netography Auto Thresholds API
The Auto Thresholds API from Netography — 3 operation(s) for auto thresholds.
Netography Block List API
The Block List API from Netography — 1 operation(s) for block list.
Netography Configuration API
The Configuration API from Netography — 1 operation(s) for configuration.
Netography Detect and Respond - Context Creation Models API
The Detect and Respond - Context Creation Models API from Netography — 6 operation(s) for detect and respond - context creation models.
Netography Detect and Respond - Detection Categories API
The Detect and Respond - Detection Categories API from Netography — 2 operation(s) for detect and respond - detection categories.
Netography Detect and Respond - Response Policies API
The Detect and Respond - Response Policies API from Netography — 5 operation(s) for detect and respond - response policies.
Netography Detect and Respond - Threshold Overrides API
The Detect and Respond - Threshold Overrides API from Netography — 4 operation(s) for detect and respond - threshold overrides.
Netography Detect and Respond - Traffic Detection Models API
The Detect and Respond - Traffic Detection Models API from Netography — 6 operation(s) for detect and respond - traffic detection models.
Netography Integrations - Context API
The Integrations - Context API from Netography — 4 operation(s) for integrations - context.
Netography Integrations - Response API
The Integrations - Response API from Netography — 3 operation(s) for integrations - response.
Netography Intelligence API
The Intelligence API from Netography — 3 operation(s) for intelligence.
Netography Labels - IPs API
The Labels - IPs API from Netography — 6 operation(s) for labels - ips.
Netography Labels - Ports API
The Labels - Ports API from Netography — 10 operation(s) for labels - ports.
Netography MITRE ATT&CK API
The MITRE ATT&CK API from Netography — 2 operation(s) for mitre att&ck.
Netography Raw Records - Fetch API
The Raw Records - Fetch API from Netography — 1 operation(s) for raw records - fetch.
Netography Raw Records - Search API
The Raw Records - Search API from Netography — 2 operation(s) for raw records - search.
Netography Resellers API
The Resellers API from Netography — 4 operation(s) for resellers.
Netography Roles API
The Roles API from Netography — 3 operation(s) for roles.
Netography Settings - Security API
The Settings - Security API from Netography — 1 operation(s) for settings - security.
Netography Settings - Traffic Classification API
The Settings - Traffic Classification API from Netography — 4 operation(s) for settings - traffic classification.
Netography Tags API
The Tags API from Netography — 5 operation(s) for tags.
Netography Traffic Sources - Devices API
The Traffic Sources - Devices API from Netography — 11 operation(s) for traffic sources - devices.
Netography Traffic Sources - DNS Devices API
The Traffic Sources - DNS Devices API from Netography — 5 operation(s) for traffic sources - dns devices.
Netography Traffic Sources - VPCs API
The Traffic Sources - VPCs API from Netography — 8 operation(s) for traffic sources - vpcs.
Netography Users API
The Users API from Netography — 3 operation(s) for users.
Scroll within the panel for all 28 ·
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.
netography-mcp.yml
MCP SERVEREvent 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.
Netography Webhooks
ASYNCAPISecurity Posture 3
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.
Resources
Every other property we hold for Netography — 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
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Company 1
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/netography · machine-readable index on apis.io