Wireshark
Wireshark is the world's foremost and widely-used free and open-source network protocol analyzer. It lets you capture and interactively browse the traffic running on a computer network. Wireshark provides a powerful dissector framework with a Lua scripting API, C/C++ plugin architecture, TShark command-line tools, and the libwireshark library for developers building network analysis tools.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Wireshark the way a machine reads it — 24 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 — Wireshark scores 25.8/100 (emerging), with a separate agent-readiness read of 7/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 Wireshark
Each block below is one kind of artifact we hold for Wireshark. 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.
Wireshark
Wireshark is a free and open-source network protocol analyzer that captures and interactively browses network traffic. It supports hundreds of protocols, runs on multiple platfo...
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.
Wireshark 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.
Wireshark 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.
Packet Capture
Capture live network traffic from multiple interfaces simultaneously using libpcap/Npcap.
Deep Packet Inspection
Analyze hundreds of protocols with full decode of packet fields and values.
Display Filters
Powerful filter language for drilling into captured traffic.
Lua Scripting
Extend Wireshark with custom dissectors, listeners, and menus using the Lua API.
Dissector Plugins
Write C/C++ plugins to add support for new protocols.
TShark CLI
Command-line version of Wireshark for scripting and automation.
Extcap Interface
Plugin API to add custom capture sources to Wireshark.
Wiretap Library
Library for reading and writing capture file formats including pcap and pcapng.
Scroll within the panel for all 8 ·
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.
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.
Network Troubleshooting
Diagnose latency, packet loss, and protocol errors in live or captured traffic.
API Traffic Debugging
Inspect raw HTTP, gRPC, and WebSocket API requests and responses at the packet level.
Protocol Development
Develop and test new network protocols using Wireshark dissectors.
Security Analysis
Analyze network traffic for intrusion indicators and malicious patterns.
Education
Learn networking concepts by capturing and examining real protocol exchanges.
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.
TShark
Command-line packet analyzer that uses the same dissection engine as Wireshark.
dumpcap
Minimal capture utility used by Wireshark and TShark.
editcap
Utility for editing and converting capture files.
Lua
Scripting language embedded in Wireshark for custom protocol dissectors.
libpcap/Npcap
Packet capture libraries used by Wireshark on Unix and Windows respectively.
Resources
Every other property we hold for Wireshark — 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 1
Reference material describing how the API behaves
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
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/wireshark · machine-readable index on apis.io