Detectify API

Name: Detectify API API
Brand: Detectify API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentSecurityVulnerability ManagementapiKey9 EndpointsREST

For Agents

Pull external attack surface data from Detectify — discovered IPs, technologies, exposed ports, and breach exposure — and manage AWS connectors used for asset discovery.

Quickstart

Get started with Detectify API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list discovered IPs from Detectify"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Detectify API API.

List every IP address Detectify has discovered across your monitored attack surface

Inventory the technologies and software versions fingerprinted on your public-facing assets

Surface every exposed port found during external surface monitoring scans

Retrieve breach exposure records tied to your monitored domains

GET STARTED

Start building with Detectify API API

Explore with Jentic

View OpenAPI Document

Use for: List all IP addresses discovered on our attack surface, Find all exposed ports on monitored assets, Retrieve the technologies fingerprinted on our public domains, Check whether any of our domains appear in breach data

Not supported: Does not handle internal authenticated vulnerability scanning, code-level SAST, or container image scanning — use for external attack surface monitoring only.

Jentic publishes the only available OpenAPI document for Detectify API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Detectify API, keeping it validated and agent-ready. Detectify is an external attack surface management and web vulnerability scanning platform. The API exposes surface monitoring data — discovered IP addresses, fingerprinted technologies, exposed ports, and known breaches — alongside connector management for AWS asset discovery. It is designed for security teams that want to feed continuous attack-surface signals into SOAR pipelines, ticketing systems, or agent workflows.

Use Cases

Patterns agents use Detectify API API for, with concrete tasks.

★ Continuous Attack Surface Inventory

Security teams use the Detectify API to maintain an always-current inventory of internet-facing assets. The /ips and /technologies endpoints expose every IP and software fingerprint Detectify has discovered through Surface Monitoring, letting teams detect shadow IT and unsanctioned cloud deployments. Inventory pulls typically run on a scheduled job and feed asset management or CMDB systems.

Call GET /ips and GET /technologies, then diff the results against yesterday's snapshot to flag newly discovered assets.

Exposed Port Alerting

The /ports endpoint returns every open port found during external scanning, useful for catching accidentally exposed services like databases, admin panels, or staging environments. Pair this with internal change-control data to spot ports that opened without an approved ticket.

Fetch GET /ports daily, compare against an allowlist of approved ports, and post a Slack alert for any non-allowlisted port.

Breach Exposure Monitoring

Use the /breaches endpoint to retrieve credential and data-breach records tied to your monitored domains. Security operations teams pipe this into incident response runbooks to force password resets and notify affected users when breach data first appears.

Poll GET /breaches every 6 hours and create a security incident ticket for each new breach record returned.

AWS Connector Lifecycle Management

The /connectors and /aws-external-id endpoints let you programmatically provision the AWS connectors that Detectify uses to discover cloud assets. This matters for organisations with many AWS accounts where manual connector setup is slow and error-prone.

Get the AWS external ID via GET /aws-external-id, then POST /connectors with the role ARN to register a new AWS account for surface monitoring.

Agent-Driven Security Triage

AI agents can use Detectify through Jentic to pull live attack surface data into triage workflows — listing exposed IPs, checking breach exposure, and reconciling asset inventories without a human curating the output. Through Jentic, the Detectify API key stays in the credential vault and the agent only sees scoped responses.

Search Jentic for 'list discovered IPs from Detectify', load the operation, and execute it with the user's stored credentials to return a deduplicated IP list.

Key Endpoints

9 endpoints — jentic publishes the only available openapi specification for detectify api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/ips

List all discovered IP addresses

GET

/technologies

List fingerprinted technologies on monitored assets

GET

/ports

List exposed ports across the surface

GET

/breaches

List breach records tied to monitored domains

GET

/connectors

List configured AWS connectors

POST

/connectors

Create a new AWS connector

DELETE

/connectors/{id}

Remove an AWS connector

GET

/aws-external-id

Fetch the AWS external ID for IAM role configuration

GET

/ips

List all discovered IP addresses

GET

/technologies

List fingerprinted technologies on monitored assets

GET

/ports

List exposed ports across the surface

GET

/breaches

List breach records tied to monitored domains

GET

/connectors

List configured AWS connectors

Why though Jentic?

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

Credential isolation

The Detectify API key is stored encrypted in the Jentic vault. Agents receive scoped execution rather than raw key access — the key is injected into the apiKeyAuth header at call time and never enters the agent's context window.

Intent-based discovery

Agents search Jentic by intent (e.g. 'list discovered IPs from Detectify'), and Jentic returns the matching Detectify operation with its input schema, so the agent calls the right endpoint without browsing Detectify documentation.

Time to first call

Direct Detectify integration: 1-2 days to handle auth, response shapes, and connector lifecycle. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Tenable Attack Surface Management

Tenable ASM is a competing external attack surface platform with broader vulnerability scoring.

Choose Tenable ASM when the workflow needs CVSS-scored vulnerabilities and integration into a wider Tenable.io vulnerability management programme.

Complementary

Snyk API

Snyk covers code, dependency, and container vulnerabilities — pair with Detectify for full external + internal coverage.

Use Snyk alongside Detectify when the agent needs to correlate external surface findings with internal code and dependency vulnerabilities.

Complementary

Tenable Nessus API

Nessus runs authenticated internal vulnerability scans that complement Detectify's unauthenticated external view.

Use Nessus when the agent needs to triage internal hosts and authenticated scan results, and use Detectify for the external attacker view.

FAQs

Specific to using Detectify API API through Jentic.

Why is there no official OpenAPI spec for Detectify API?

Detectify does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Detectify API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Detectify API use?

Detectify uses an API key passed in a request header (apiKeyAuth scheme). Through Jentic, the key is stored encrypted in the credential vault and injected at execution time, so the raw key never enters the agent's context.

Can I list every IP address Detectify has discovered with the Detectify API?

Yes — call GET /ips to retrieve every IP address Detectify has discovered through Surface Monitoring. The response includes all monitored assets and can be diffed against prior snapshots to detect newly exposed infrastructure.

What are the rate limits for the Detectify API?

Detectify does not publish rate limits in the OpenAPI spec. Treat the API as conservatively rate-limited and cache responses for asset inventory pulls; surface monitoring data does not change second-to-second.

How do I set up an AWS connector through Jentic?

Search Jentic for 'create AWS connector in Detectify', load the operation, then call GET /aws-external-id to get the external ID, configure the IAM role in AWS, and POST /connectors with the role ARN. The full flow runs through Jentic's search, load, execute pattern.

Can I retrieve breach exposure data for my domains with the Detectify API?

Yes — GET /breaches returns breach records tied to the domains under your monitored attack surface. Poll this endpoint on a schedule and pipe new records into incident response workflows.