Shodan API

Name: Shodan API
Brand: Shodan API
Availability: InStock

✓ Official Vendor SpecSecurityVulnerability ManagementapiKey41 EndpointsREST

For Agents

Programmatically returns all services found on given host ip, search shodan without results, returns only total count. Covers 41 operations with apiKey authentication.

Install Jentic One Beta

Connect the Shodan API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Shodan 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 Shodan API.

Returns all services found on given host IP

Search Shodan without results, returns only total count

Break the search query into tokens

Query and filter Shodan API records by parameters

GET STARTED

Start building with Shodan API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Shodan API for, with concrete tasks.

★ Security Operations

Use the Shodan API to perform security operations programmatically. The API provides 41 endpoints covering core functionality including returns all services found on given host ip, search shodan without results, returns only total count, search shodan using the same query syntax as the website.

Call GET /shodan/host/{ip} to returns all services found on given host ip

Automated Account Management

Automate account operations by combining multiple Shodan API endpoints. Agents can search shodan without results, returns only total count and then search shodan using the same query syntax as the website in a single workflow.

Call GET /shodan/host/count to search shodan without results, returns only total count, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Shodan API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Search Jentic for 'returns all services found on given host ip', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

41 endpoints — shodan is the world's first search engine for internet-connected devices.

METHOD

PATH

DESCRIPTION

GET

/shodan/host/{ip}

Returns all services found on given host IP

GET

/shodan/host/count

Search Shodan without results, returns only total count

GET

/shodan/host/search

Search Shodan using the same query syntax as the website

GET

/shodan/host/search/facets

Returns a list of facets for breakdown info

GET

/shodan/host/search/filters

Returns a list of search filters for queries

GET

/shodan/host/search/tokens

Break the search query into tokens

GET

/shodan/ports

Returns list of port numbers crawlers look for

GET

/shodan/protocols

Returns protocols available for Internet scans

GET

/shodan/host/{ip}

Returns all services found on given host IP

GET

/shodan/host/count

Search Shodan without results, returns only total count

GET

/shodan/host/search

Search Shodan using the same query syntax as the website

GET

/shodan/host/search/facets

Returns a list of facets for breakdown info

GET

/shodan/host/search/filters

Returns a list of search filters for queries

Why Jentic?

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

Credential isolation

Your Shodan key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'look up services on a host IP' or 'count matching search results', and Jentic returns the matching Shodan operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Snyk

Alternative security API

Choose Snyk when you need a different approach to security operations

Alternative

Crowdstrike

Alternative security API

Choose Crowdstrike when you need a different approach to security operations

FAQs

Specific to using Shodan API through Jentic.

What authentication does the Shodan API use?

The Shodan API uses an API key passed in the `key` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I returns all services found on given host ip with the Shodan API?

Yes. Use the GET /shodan/host/{ip} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Shodan API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I returns all services found on given host ip through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'returns all services found on given host ip'. Jentic returns the matching Shodan API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Shodan API have?

The Shodan API exposes 41 endpoints covering account, alerts, bulk data operations.

Can I limit what my agent is allowed to do with the Shodan API?

Yes. Because you run Jentic One yourself, your own rules decide which Shodan operations and credentials the agent can use. Since every Shodan operation in this spec is a read-only lookup over hosts, search, ports, and protocols, you can allow just the ones the agent needs, such as GET /shodan/host/{ip} for host lookup by IP or GET /shodan/host/count for a search count, and it can call nothing beyond the read operations you approve.