Patrowl Engines API

Name: Patrowl Engines API
Brand: Patrowl Engines API
Availability: InStock

✓ Official Vendor SpecSecurityVulnerability Managementnone14 EndpointsREST

For Agents

Control Patrowl security scanning engines to start vulnerability scans, check scan progress, retrieve findings, and manage engine configurations across Nmap, SSLLabs, Arachni, and other scanners.

Install Jentic One Beta

Connect the Patrowl Engines API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Patrowl Engines API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Patrowl Engines API.

Initiate security scans against target hosts using multiple engine types

Monitor scan execution status and retrieve progress updates by scan ID

Retrieve structured vulnerability findings after scan completion

GET STARTED

Start building with Patrowl Engines API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Patrowl Engines API for, with concrete tasks.

★ Automated Vulnerability Scanning

Initiate security scans against target hosts or networks using the /startscan endpoint. Patrowl engines support various scan types including port scanning (Nmap), SSL certificate analysis (SSLLabs), web application scanning (Arachni), and DNS reconnaissance (Owl DNS). Each scan receives a unique ID for status tracking and result retrieval.

Start a scan via POST /startscan with target 'example.com' and scan type 'nmap_portscan', then poll GET /status/{scanId} until completion

Security Findings Collection

Retrieve structured vulnerability findings after scan completion through the /getfindings/{scanId} endpoint. Findings include severity levels, affected hosts, vulnerability descriptions, and remediation guidance. This enables automated security reporting, vulnerability tracking, and integration with ticketing systems for remediation workflows.

Retrieve findings from scan ID 'scan_456' via GET /getfindings/{scanId} and extract all findings with severity 'high' or 'critical'

Engine Health Monitoring

Monitor scanning engine availability and readiness using the /liveness and /readiness endpoints. These health checks verify that the engine process is running and capable of accepting new scans. This supports orchestration platforms that need to route scan requests to healthy engine instances.

Check engine health via GET /liveness and GET /readiness, then retrieve engine info via GET /info to confirm available scan capabilities

AI Agent Security Scan Orchestration

AI agents orchestrate security scans through Jentic by discovering scan operations, initiating scans against targets, and collecting findings without managing engine connectivity directly. Agents search for security scanning operations and receive structured schemas for the standardized Patrowl engine interface.

Search Jentic for 'start a vulnerability scan', load the schema for POST /startscan, execute against target 'test.example.com', then retrieve findings via GET /getfindings/{scanId}

Key Endpoints

14 endpoints — the patrowl engines api provides a rest interface for controlling security scanning engines including nmap, ssllabs, arachni, virustotal, and others.

METHOD

PATH

DESCRIPTION

POST

/startscan

Initiate a new security scan

GET

/status/{scanId}

Check scan progress by ID

GET

/getfindings/{scanId}

Retrieve scan findings

GET

/stop/{scanId}

Stop a running scan

GET

/liveness

Engine liveness health check

GET

/readiness

Engine readiness check

GET

/info

Get engine information and capabilities

GET

/clean/{scanId}

Clean scan data by ID

POST

/startscan

Initiate a new security scan

GET

/status/{scanId}

Check scan progress by ID

GET

/getfindings/{scanId}

Retrieve scan findings

GET

/stop/{scanId}

Stop a running scan

GET

/liveness

Engine liveness health check

GET

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Patrowl runs without authentication by default. When network-level credentials are required, Jentic stores access tokens in its vault and injects them into requests, isolating engine access from the agent context.

Intent-based discovery

Agents search by intent (e.g., 'start a vulnerability scan against a host') and Jentic returns the matching Patrowl operation with parameter schemas for target specification and scan configuration.

Time to first call

Direct Patrowl integration: 1-2 days for engine setup, scan workflow implementation, and finding parsing. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Patrowl Engines API through Jentic.

What authentication does the Patrowl Engines API use?

The Patrowl Engines API does not require authentication by default as it is designed to run on localhost. Security is managed at the network level by restricting access to the engine ports (5001-5014). When deploying in production, network-level access controls or a reverse proxy with authentication should be used.

Which scanning engines does Patrowl support?

Patrowl supports multiple scanning engines each running on dedicated ports: Nmap (port 5001) for port scanning, SSLLabs (5004) for SSL analysis, Arachni (5005) for web application scanning, Owl DNS (5006) for DNS reconnaissance, VirusTotal (5007) for malware checks, URLVoid (5008) for URL reputation, Cortex (5009) for threat intelligence, and several others.

How do I retrieve vulnerability findings from a scan?

After starting a scan via POST /startscan, poll GET /status/{scanId} until the scan status shows completion. Then retrieve structured findings via GET /getfindings/{scanId}. Findings include severity level, affected target, description, and remediation guidance. Results can be cleaned after processing via GET /clean/{scanId}.

Can I stop a running scan?

Yes. Individual scans can be stopped via GET /stop/{scanId} using the scan ID returned when the scan was started. To stop all running scans on an engine, use GET /stopscans. Partially completed scans may still have findings available via the getfindings endpoint.

How do I start a security scan through Jentic?

Search Jentic for 'start a security vulnerability scan', load the operation schema for POST /startscan, and execute with target and scan configuration parameters. Jentic handles the engine routing and returns structured findings. Install with pip install jentic.

What is the difference between liveness and readiness endpoints?

GET /liveness confirms the engine process is running and responsive. GET /readiness confirms the engine is configured and capable of accepting new scan requests. An engine may be alive but not ready if it is still loading configuration or has reached maximum concurrent scan capacity.