Tenable Identity Exposure

Name: Identity Exposure API
Brand: Identity Exposure
Availability: InStock

✓ Official Vendor SpecIdentity AuthAuthenticationapiKey131 EndpointsREST

Install Jentic One Beta

Connect the Identity Exposure to your agent

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

Get about singleton.

Return the last state of every ad-object at the provided timestampBy default, th

Retrieve an AD object by id that have deviances for a specific profile and check

GET STARTED

Start building with Identity Exposure API

Explore with Jentic

View OpenAPI Document

For Agents

Programmatically get about singleton., return the last state of every ad-object at the provided timestampby default, th. Covers 131 operations with apiKey authentication.

Use for: I need to about singleton., I want to return the last state of every ad-object at the provided timestampby default, th, Search for ad-object instance by id., Find all ad-object instance by id.

Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.

Use Cases

Patterns agents use Identity Exposure API for, with concrete tasks.

★ Identity and Authentication Operations

Use the Identity Exposure to perform identity auth operations programmatically. The API provides 131 endpoints covering core functionality including get about singleton., return the last state of every ad-object at the provided timestampby default, th, get ad-object instance by id..

Call GET /api/about to get about singleton.

Automated About Management

Automate about operations by combining multiple Identity Exposure endpoints. Agents can return the last state of every ad-object at the provided timestampby default, th and then get ad-object instance by id. in a single workflow.

Call GET /api/ad-objects to return the last state of every ad-object at the provided timestampby default, th, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Identity Exposure 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 about singleton.', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

131 endpoints — api to interact with identity exposure.

METHOD

PATH

DESCRIPTION

GET

/api/about

Get about singleton.

GET

/api/ad-objects

Return the last state of every ad-object at the provided timestampBy default, th

GET

/api/directories/{directoryId}/ad-objects/{id}

Get ad-object instance by id.

GET

/api/infrastructures/{infrastructureId}/directories/{directoryId}/ad-objects/{id}

Get ad-object instance by id.

GET

/api/profiles/{profileId}/checkers/{checkerId}/ad-objects/{id}

Retrieve an AD object by id that have deviances for a specific profile and check

GET

/api/infrastructures/{infrastructureId}/directories/{directoryId}/events/{eventId}/ad-objects/{id}

Get one ad-object by event and by id

GET

/api/infrastructures/{infrastructureId}/directories/{directoryId}/events/{eventId}/ad-objects/{id}/changes

Get one ad-object changes between a given event and the event which precedes it

POST

/api/profiles/{profileId}/checkers/{checkerId}/ad-objects/search

Search all AD objects having deviances by profile by checker

GET

/api/about

Get about singleton.

GET

/api/ad-objects

Return the last state of every ad-object at the provided timestampBy default, th

GET

/api/directories/{directoryId}/ad-objects/{id}

Get ad-object instance by id.

GET

/api/infrastructures/{infrastructureId}/directories/{directoryId}/ad-objects/{id}

Get ad-object instance by id.

GET

/api/profiles/{profileId}/checkers/{checkerId}/ad-objects/{id}

Retrieve an AD object by id that have deviances for a specific profile and check

Why Jentic?

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

Credential isolation

Your Identity Exposure API 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 'list AD objects' or 'read directory events', and Jentic returns the matching Identity Exposure operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Identity Exposure API through Jentic.

What authentication does the Identity Exposure use?

The Identity Exposure uses an API key passed in the `x-api-key` 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 get about singleton. with the Identity Exposure?

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

What are the rate limits for the Identity Exposure?

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 about singleton. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get about singleton.'. Jentic returns the matching Identity Exposure operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Identity Exposure have?

The Identity Exposure exposes 131 endpoints covering about, ad object, alert operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Identity Exposure operations and credentials the agent may use. Since the API carries the directory id in the URL path (for example /api/directories/{directoryId}/ad-objects/{id}), you can pin the agent to a single directory and grant only read access to its AD objects and events, such as GET /api/ad-objects. Any operation you do not add stays off limits, so the agent cannot reach beyond the reads you allowed.

Tenable Identity Exposure

Connect the Identity Exposure to your agent

Capabilities

Start building with Identity Exposure API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs