ProjectDiscovery
ProjectDiscovery builds the open-source security toolchain trusted across offensive security and attack-surface management -- Nuclei, Subfinder, httpx, Katana, Naabu, dnsx and more -- and the ProjectDiscovery Cloud Platform (PDCP) that operationalizes them for continuous exposure management. Its REST API at api.projectdiscovery.io exposes asset discovery and enumeration, template-driven vulnerability scanning, credential-leak monitoring, scan scheduling, configuration, and template management, authenticated with a single X-API-Key header over HTTPS. Founded by the creators of Nuclei and backed by Accel, ProjectDiscovery serves security teams automating attack-surface discovery and vulnerability detection at scale.
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 ProjectDiscovery the way a machine reads it — 25 machine-readable artifacts across 20 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 — ProjectDiscovery scores 55.4/100 (developing), with a separate agent-readiness read of 51/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 ProjectDiscovery
Each block below is one kind of artifact we hold for ProjectDiscovery. 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 20
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.
ProjectDiscovery Asset API
The Asset API from ProjectDiscovery — 8 operation(s) for asset.
ProjectDiscovery assets API
The assets API from ProjectDiscovery — 3 operation(s) for assets.
ProjectDiscovery chaos API
The chaos API from ProjectDiscovery — 1 operation(s) for chaos.
ProjectDiscovery configurations API
The configurations API from ProjectDiscovery — 6 operation(s) for configurations.
ProjectDiscovery enumerations API
The enumerations API from ProjectDiscovery — 11 operation(s) for enumerations.
ProjectDiscovery export API
The export API from ProjectDiscovery — 2 operation(s) for export.
ProjectDiscovery history API
The history API from ProjectDiscovery — 1 operation(s) for history.
ProjectDiscovery internal API
The internal API from ProjectDiscovery — 3 operation(s) for internal.
ProjectDiscovery Leaks API
The Leaks API from ProjectDiscovery — 5 operation(s) for leaks.
ProjectDiscovery results API
The results API from ProjectDiscovery — 4 operation(s) for results.
ProjectDiscovery retests API
The retests API from ProjectDiscovery — 1 operation(s) for retests.
ProjectDiscovery scan_log API
The scan_log API from ProjectDiscovery — 1 operation(s) for scan_log.
ProjectDiscovery scans API
The scans API from ProjectDiscovery — 17 operation(s) for scans.
ProjectDiscovery Team API
The Team API from ProjectDiscovery — 2 operation(s) for team.
ProjectDiscovery Template API
The Template API from ProjectDiscovery — 1 operation(s) for template.
ProjectDiscovery template/v2 API
The template/v2 API from ProjectDiscovery — 1 operation(s) for template/v2.
ProjectDiscovery templates API
The templates API from ProjectDiscovery — 9 operation(s) for templates.
ProjectDiscovery users API
The users API from ProjectDiscovery — 2 operation(s) for users.
ProjectDiscovery vuln API
The vuln API from ProjectDiscovery — 1 operation(s) for vuln.
ProjectDiscovery Vulnerability API
The Vulnerability API from ProjectDiscovery — 4 operation(s) for vulnerability.
Scroll within the panel for all 20 ·
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.
projectdiscovery-mcp.yml
MCP SERVERSecurity Posture 4
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.
Projectdiscovery Trust Center
SOC 2 Type 2, EU-US Data Privacy Framework (DPF), UK Extension to EU-US DPF
SECURITYResources
Every other property we hold for ProjectDiscovery — 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 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/projectdiscovery · machine-readable index on apis.io