Anexya Basic Audit Plugin APIs

Name: Basic Audit Plugin APIs
Brand: Basic Audit Plugin APIs
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthAuthenticationapiKey3 Endpoints

Install Jentic One Beta

Connect the Basic Audit Plugin APIs to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Basic Audit Plugin APIs, 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 Basic Audit Plugin APIs.

Authenticates to the Audit plugin.

Create and start an audit operation

Complete and stop an already running audit operation

Query and filter Basic Audit Plugin APIs records by parameters

GET STARTED

Start building with Basic Audit Plugin APIs

Explore with Jentic

View OpenAPI Document

For Agents

Programmatically authenticates to the audit plugin., create and start an audit operation. Covers 3 operations with apiKey authentication.

Use for: I need to authenticates to the audit plugin., I want to and start an audit operation, Search for complete and stop an already running audit operation, List all records from Basic Audit Plugin APIs

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

Use Cases

Patterns agents use Basic Audit Plugin APIs for, with concrete tasks.

★ Identity and Authentication Operations

Use the Basic Audit Plugin APIs to perform identity auth operations programmatically. The API provides 3 endpoints covering core functionality including authenticates to the audit plugin., create and start an audit operation, complete and stop an already running audit operation.

Call PUT /audit/api/v1/auth to authenticates to the audit plugin.

Automated authentication Management

Automate authentication operations by combining multiple Basic Audit Plugin APIs endpoints. Agents can create and start an audit operation and then complete and stop an already running audit operation in a single workflow.

Call POST /audit/api/v1/audit/logicaldevices/{logicalDeviceName}/types/audit to create and start an audit operation, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Basic Audit Plugin APIs 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 'authenticates to the audit plugin.', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

3 endpoints — apis to authenticate and manipulate audit operations.

METHOD

PATH

DESCRIPTION

PUT

/audit/api/v1/auth

Authenticates to the Audit plugin.

POST

/audit/api/v1/audit/logicaldevices/{logicalDeviceName}/types/audit

Create and start an audit operation

POST

/audit/api/v1/audit/logicaldevices/{logicalDeviceName}/types/audit/complete

Complete and stop an already running audit operation

PUT

/audit/api/v1/auth

Authenticates to the Audit plugin.

POST

/audit/api/v1/audit/logicaldevices/{logicalDeviceName}/types/audit

Create and start an audit operation

POST

/audit/api/v1/audit/logicaldevices/{logicalDeviceName}/types/audit/complete

Complete and stop an already running audit operation

Why Jentic?

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

Credential isolation

Your Basic Audit session credential 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 'run an audit for a logical device' or 'authenticate to the audit plugin', and Jentic returns the matching 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 Basic Audit Plugin APIs through Jentic.

What authentication does the Basic Audit Plugin APIs use?

The Basic Audit Plugin APIs uses an API key passed in the `JSESSIONID` cookie. 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 authenticates to the audit plugin. with the Basic Audit Plugin APIs?

Yes. Use the PUT /audit/api/v1/auth endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Basic Audit Plugin APIs?

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 authenticates to the audit plugin. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'authenticates to the audit plugin.'. Jentic returns the matching Basic Audit Plugin APIs operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Basic Audit Plugin APIs have?

The Basic Audit Plugin APIs exposes 3 endpoints covering authentication, audit operations.

Can I limit what my agent is allowed to do with the Basic Audit Plugin APIs?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. Since this API carries the logical device name in the URL path, you can pin the agent to a single logical device so it can only authenticate, start audits, and complete audits for that device. Any operation you leave out of your rules stays unavailable to the agent.

Anexya Basic Audit Plugin APIs

Connect the Basic Audit Plugin APIs to your agent

Capabilities

Start building with Basic Audit Plugin APIs

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs