Pulsedive API

Name: Pulsedive API API
Brand: Pulsedive API
Availability: InStock

✓ Official Vendor SpecSecurityThreat DetectionapiKey8 EndpointsREST

For Agents

Programmatically get indicator by id, get indicator by value. Covers 8 operations with apiKey authentication.

Use for: I need to indicator by id, I want to indicator by value, Search for threat by id, Find all threat by name

Quickstart

Get started with Pulsedive 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:
"get indicator by id"

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

Capabilities

What an agent can do with Pulsedive API API.

Get indicator by ID

Explore indicators

Submit indicator for scanning

Use Cases

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

GET STARTED

Start building with Pulsedive API API

Explore with Jentic

View OpenAPI Document

Automated Indicators Management

Automate indicators operations by combining multiple Pulsedive API endpoints. Agents can get indicator by value and then get threat by id in a single workflow.

Call GET /info.php#indicator-by-value to get indicator by value, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Pulsedive 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 'get indicator by id', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

8 endpoints — pulsedive is a free threat intelligence platform that provides community-powered indicator of compromise (ioc) data.

METHOD

PATH

DESCRIPTION

GET

/info.php

Get indicator by ID

GET

/info.php#indicator-by-value

Get indicator by value

GET

/info.php#threat

Get threat by ID

GET

/info.php#threat-by-name

Get threat by name

GET

/info.php#feed

Get feed by ID

GET

/explore.php

Explore indicators

POST

/analyze.php

Submit indicator for scanning

GET

/analyze.php

Get scan results

GET

/info.php

Get indicator by ID

GET

/info.php#indicator-by-value

Get indicator by value

GET

/info.php#threat

Get threat by ID

GET

/info.php#threat-by-name

Get threat by name

GET

/info.php#feed

Get feed by ID

GET

Why though Jentic?

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

Credential isolation

Pulsedive API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'get indicator by id') and Jentic returns the matching Pulsedive API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Pulsedive API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

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 Pulsedive API API through Jentic.

What authentication does the Pulsedive API use?

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

Can I get indicator by id with the Pulsedive API?

Yes. Use the GET /info.php endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Pulsedive 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 get indicator by id through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'get indicator by id'. Jentic returns the matching Pulsedive API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Pulsedive API have?

The Pulsedive API exposes 8 endpoints covering indicators, threats, explore operations.