ThreatJammer.com User API

Name: ThreatJammer.com User API
Brand: ThreatJammer.com User API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMCustomer Supportbearer96 EndpointsREST

For Agents

Programmatically creates a new private allowlist binded to the user., get the set of private allowlists of the user.. Covers 96 operations with bearer authentication.

Install Jentic One Beta

Connect the ThreatJammer.com User API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ThreatJammer.com User 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fthreatjammer.com%2Fthreatjammer" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fthreatjammer.com%2Fthreatjammer" | 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 ThreatJammer.com User API.

Creates a new private allowlist binded to the user.

Get the set of private allowlists of the user.

Update the information of an existing private allowlist of the user.

GET STARTED

Start building with ThreatJammer.com User API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use ThreatJammer.com User API for, with concrete tasks.

★ CRM Operations

Use the ThreatJammer.com User API to perform crm operations programmatically. The API provides 96 endpoints covering core functionality including creates a new private allowlist binded to the user., get the set of private allowlists of the user., get the set of private allowlists of the user by resource type..

Call POST /v1/allowlist/private to creates a new private allowlist binded to the user.

Automated Allowlist Management

Automate allowlist operations by combining multiple ThreatJammer.com User API endpoints. Agents can get the set of private allowlists of the user. and then get the set of private allowlists of the user by resource type. in a single workflow.

Call GET /v1/allowlist/private/all to get the set of private allowlists of the user., then verify the result

AI Agent Integration via Jentic

AI agents discover and call ThreatJammer.com User 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 bearer tokens manually.

Search Jentic for 'creates a new private allowlist binded to the user.', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

96 endpoints — the public api open to the users.

METHOD

PATH

DESCRIPTION

POST

/v1/allowlist/private

Creates a new private allowlist binded to the user.

GET

/v1/allowlist/private/all

Get the set of private allowlists of the user.

GET

/v1/allowlist/private/all/{resource_type}

Get the set of private allowlists of the user by resource type.

GET

/v1/allowlist/private/ip/{address}

Get the different private allowlists where the IP address was found.

GET

/v1/allowlist/private/{allowlist_id}

Get the details of a specific private allowlist of the user.

PUT

/v1/allowlist/private/{allowlist_id}

Update the information of an existing private allowlist of the user.

DELETE

/v1/allowlist/private/{allowlist_id}

Delete all the bindings between a user and a private allowlist.

GET

/v1/allowlist/private/{allowlist_id}/content

Get the content of a private allowlist of the user.

POST

/v1/allowlist/private

Creates a new private allowlist binded to the user.

GET

/v1/allowlist/private/all

Get the set of private allowlists of the user.

GET

/v1/allowlist/private/all/{resource_type}

Get the set of private allowlists of the user by resource type.

GET

/v1/allowlist/private/ip/{address}

Get the different private allowlists where the IP address was found.

GET

/v1/allowlist/private/{allowlist_id}

Get the details of a specific private allowlist of the user.

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the ThreatJammer.com User API by hand means learning its bearer auth, targeting the Dublin host, and managing the private allowlist calls yourself. Through Jentic you install once, import the ThreatJammer.com User API from the API Directory, store the token once, and your agent calls it.

Permission scoping

ThreatJammer puts the allowlist id in the URL path (/v1/allowlist/private/{allowlist_id}), so a rule can pin your agent to one private allowlist: it can read that list and its content and nothing else. You choose the operations it may call, so destructive ones like updating or deleting an allowlist are not included unless you add them.

Credential isolation

Your ThreatJammer token 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 'create a private allowlist' or 'check if an IP is allowlisted', and Jentic returns the matching ThreatJammer.com User API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using ThreatJammer.com User API through Jentic.

What authentication does the ThreatJammer.com User API use?

The ThreatJammer.com User API uses a Bearer token in the Authorization header. 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 creates a new private allowlist binded to the user. with the ThreatJammer.com User API?

Yes. Use the POST /v1/allowlist/private endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the ThreatJammer.com User 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 creates a new private allowlist binded to the user. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'creates a new private allowlist binded to the user.'. Jentic returns the matching ThreatJammer.com User API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the ThreatJammer.com User API have?

The ThreatJammer.com User API exposes 96 endpoints covering allowlist, asn, assess operations.

Can I limit what my agent is allowed to do with the ThreatJammer.com User API?

Yes. Jentic One is self-hosted, so your own rules decide which ThreatJammer operations and credentials the agent may use. Because ThreatJammer puts the allowlist id in the URL path, such as /v1/allowlist/private/{allowlist_id}, a rule can pin the agent to a single private allowlist so it only reads that list and its content. You choose the operations it may call, so destructive ones like PUT or DELETE on an allowlist are excluded unless you add them.

ThreatJammer.com User API

Connect the ThreatJammer.com User API to your agent

Capabilities

Start building with ThreatJammer.com User API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs