OWASP ZAP
OWASP ZAP (Zed Attack Proxy) is an open source web application security scanner for finding vulnerabilities in APIs and web applications during development and testing. ZAP exposes a comprehensive HTTP API for controlling and automating scans, spidering, authentication, alerts, reporting, and more.
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 OWASP ZAP the way a machine reads it — 57 machine-readable artifacts across 49 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 — OWASP ZAP scores 39.3/100 (thin), with a separate agent-readiness read of 48/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 OWASP ZAP
Each block below is one kind of artifact we hold for OWASP ZAP. 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 49
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.
OWASP ZAP accessControl API
The accessControl API from OWASP ZAP — 4 operation(s) for accesscontrol.
OWASP ZAP acsrf API
The acsrf API from OWASP ZAP — 6 operation(s) for acsrf.
OWASP ZAP ajaxSpider API
The ajaxSpider API from OWASP ZAP — 41 operation(s) for ajaxspider.
OWASP ZAP alert API
The alert API from OWASP ZAP — 13 operation(s) for alert.
OWASP ZAP alertFilter API
The alertFilter API from OWASP ZAP — 12 operation(s) for alertfilter.
OWASP ZAP ascan API
The ascan API from OWASP ZAP — 90 operation(s) for ascan.
OWASP ZAP authentication API
The authentication API from OWASP ZAP — 8 operation(s) for authentication.
OWASP ZAP authorization API
The authorization API from OWASP ZAP — 2 operation(s) for authorization.
OWASP ZAP automation API
The automation API from OWASP ZAP — 3 operation(s) for automation.
OWASP ZAP autoupdate API
The autoupdate API from OWASP ZAP — 32 operation(s) for autoupdate.
OWASP ZAP break API
The break API from OWASP ZAP — 11 operation(s) for break.
OWASP ZAP client API
The client API from OWASP ZAP — 5 operation(s) for client.
OWASP ZAP clientSpider API
The clientSpider API from OWASP ZAP — 3 operation(s) for clientspider.
OWASP ZAP context API
The context API from OWASP ZAP — 21 operation(s) for context.
OWASP ZAP core API
The core API from OWASP ZAP — 97 operation(s) for core.
OWASP ZAP custompayloads API
The custompayloads API from OWASP ZAP — 8 operation(s) for custompayloads.
OWASP ZAP dev API
The dev API from OWASP ZAP — 1 operation(s) for dev.
OWASP ZAP exim API
The exim API from OWASP ZAP — 9 operation(s) for exim.
OWASP ZAP forcedUser API
The forcedUser API from OWASP ZAP — 4 operation(s) for forceduser.
OWASP ZAP graphql API
The graphql API from OWASP ZAP — 20 operation(s) for graphql.
OWASP ZAP httpSessions API
The httpSessions API from OWASP ZAP — 16 operation(s) for httpsessions.
OWASP ZAP hud API
The hud API from OWASP ZAP — 37 operation(s) for hud.
OWASP ZAP keyboard API
The keyboard API from OWASP ZAP — 2 operation(s) for keyboard.
OWASP ZAP localProxies API
The localProxies API from OWASP ZAP — 3 operation(s) for localproxies.
OWASP ZAP network API
The network API from OWASP ZAP — 48 operation(s) for network.
OWASP ZAP oast API
The oast API from OWASP ZAP — 11 operation(s) for oast.
OWASP ZAP openapi API
The openapi API from OWASP ZAP — 2 operation(s) for openapi.
OWASP ZAP paramDigger API
The paramDigger API from OWASP ZAP — 1 operation(s) for paramdigger.
OWASP ZAP params API
The params API from OWASP ZAP — 1 operation(s) for params.
OWASP ZAP pnh API
The pnh API from OWASP ZAP — 8 operation(s) for pnh.
OWASP ZAP postman API
The postman API from OWASP ZAP — 2 operation(s) for postman.
OWASP ZAP pscan API
The pscan API from OWASP ZAP — 17 operation(s) for pscan.
OWASP ZAP quickstartlaunch API
The quickstartlaunch API from OWASP ZAP — 1 operation(s) for quickstartlaunch.
OWASP ZAP replacer API
The replacer API from OWASP ZAP — 4 operation(s) for replacer.
OWASP ZAP reports API
The reports API from OWASP ZAP — 3 operation(s) for reports.
OWASP ZAP retest API
The retest API from OWASP ZAP — 1 operation(s) for retest.
OWASP ZAP reveal API
The reveal API from OWASP ZAP — 2 operation(s) for reveal.
OWASP ZAP revisit API
The revisit API from OWASP ZAP — 3 operation(s) for revisit.
OWASP ZAP ruleConfig API
The ruleConfig API from OWASP ZAP — 5 operation(s) for ruleconfig.
OWASP ZAP script API
The script API from OWASP ZAP — 24 operation(s) for script.
OWASP ZAP search API
The search API from OWASP ZAP — 18 operation(s) for search.
OWASP ZAP selenium API
The selenium API from OWASP ZAP — 22 operation(s) for selenium.
OWASP ZAP sessionManagement API
The sessionManagement API from OWASP ZAP — 4 operation(s) for sessionmanagement.
OWASP ZAP soap API
The soap API from OWASP ZAP — 2 operation(s) for soap.
OWASP ZAP spider API
The spider API from OWASP ZAP — 71 operation(s) for spider.
OWASP ZAP stats API
The stats API from OWASP ZAP — 13 operation(s) for stats.
OWASP ZAP users API
The users API from OWASP ZAP — 15 operation(s) for users.
OWASP ZAP wappalyzer API
The wappalyzer API from OWASP ZAP — 3 operation(s) for wappalyzer.
OWASP ZAP websocket API
The websocket API from OWASP ZAP — 6 operation(s) for websocket.
Scroll within the panel for all 49 ·
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).
ZAP API
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.
Owasp Zap 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.
Owasp Zap Finops
FINOPSSecurity 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 OWASP ZAP — 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
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
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/owasp-zap · machine-readable index on apis.io