Install Jentic One Beta

Connect the Mitigant Cloud Security API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Mitigant Cloud Security 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%2Fmitigant.io%2Fmitigant" | 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%2Fmitigant.io%2Fmitigant" | 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 Mitigant Cloud Security API.

Connect AWS, Azure, and GCP accounts for posture scanning

Trigger and monitor cloud security scans on demand

List and filter findings by severity, asset, or compliance control

Inventory cloud assets discovered during scans

Run attack simulations against connected cloud environments

GET STARTED

Start building with Mitigant Cloud Security API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Mitigant Cloud Security API for, with concrete tasks.

★ Continuous Cloud Posture Monitoring

Integrate Mitigant into a security operations workflow that triggers scans on a schedule and pulls new findings into the SOC ticketing system. The API exposes scan creation, status, and findings retrieval so a script can run nightly, route critical findings to engineers, and close out resolved items based on subsequent scan results.

Trigger a scan on cloud account {accountId} via POST /scans, poll status, and post any critical findings to the SOC channel

Attack Surface Discovery

Use the assets endpoints to enumerate the publicly exposed surface of a multi-cloud estate after an account is connected. The discovered assets are correlated with findings so security teams can see which exposed resources have outstanding misconfigurations or vulnerabilities, prioritising remediation by blast radius rather than raw severity.

Call GET /assets filtered by exposed=true and intersect with /findings to list public assets carrying critical findings

Chaos-Style Attack Simulation

Run controlled attack simulations against staging cloud environments to validate detection and response controls. The simulation endpoints orchestrate techniques like over-permissive IAM policy abuse or storage exfiltration patterns and report whether existing alarms or guardrails fired, so red-team and detection-engineering exercises can be automated rather than manual.

Trigger an attack simulation on staging account {accountId} and capture the simulation result for the detection-engineering report

Agent-Driven Cloud Security Triage

An agent discovered through Jentic queries Mitigant findings, opens tickets in the engineering tracker for unresolved critical items, and re-checks the next day to confirm closure. Jentic isolates the bearer token in its credential vault so the agent only invokes scoped operations rather than handling raw secrets.

Use Jentic to find Mitigant's findings list operation, retrieve open critical findings, and open a tracker ticket for each one not already triaged

Key Endpoints

20 endpoints — jentic publishes the only available openapi specification for mitigant cloud security api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/cloud-accounts

List connected cloud accounts

POST

/scans

Trigger a security scan

GET

/findings

List security findings

GET

/assets

List discovered cloud assets

GET

/scans/{scanId}

Get scan status

GET

/findings/{findingId}

Get details for a specific finding

GET

/cloud-accounts

List connected cloud accounts

POST

/scans

Trigger a security scan

GET

/findings

List security findings

GET

/assets

List discovered cloud assets

GET

/scans/{scanId}

Get scan status

GET

/findings/{findingId}

Get details for a specific finding

Why Jentic?

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

Setup

Wiring the Mitigant Cloud Security API by hand means handling its bearer auth, tracking scan and finding ids across calls, and plumbing posture and asset reads yourself. Through Jentic you install once, import the Mitigant Cloud Security API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Mitigant puts the scan and finding ids in the URL path (/scans/{scanId}, /findings/{findingId}), so a rule can pin your agent to read-only posture work: it can list cloud accounts, assets, and findings and inspect one scan. You choose the operations it may call, so starting an attack simulation with a new scan is not included unless you add it.

Credential isolation

Your Mitigant 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 'list cloud security findings' or 'check an account's posture', and Jentic returns the matching Mitigant operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Mitigant Cloud Security API through Jentic.

Why is there no official OpenAPI spec for Mitigant Cloud Security API?

Mitigant does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Mitigant Cloud Security API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Mitigant Cloud Security API use?

The API uses bearer token authentication. The token is generated from the Mitigant console and passed in the Authorization header. Through Jentic the bearer is held in the credential vault and injected at execution time so agent code never sees the raw token.

Can I trigger a scan and retrieve findings with the Mitigant API?

Yes. Call POST /scans with the cloud account identifier to start a scan, poll GET /scans/{scanId} for status, then call GET /findings filtered by the resulting scan to retrieve the security findings.

What are the rate limits for the Mitigant Cloud Security API?

Mitigant applies per-tenant rate limits that depend on your subscription tier. Scan creation and attack simulation calls are stricter than findings reads. Check your Mitigant console for current numeric limits before automating large batches.

How do I list open critical findings through Jentic?

Search Jentic for list mitigant findings, load the schema for GET /findings, and execute with the severity filter set to critical. The structured response can be passed directly to a ticketing integration.

Does the Mitigant API support attack simulation?

Yes. The Attack Simulations endpoints orchestrate controlled adversary techniques against connected cloud accounts and report whether expected detections fired. Use them on staging accounts to validate detection and response controls.

Can I limit what my agent is allowed to do with the Mitigant Cloud Security API?

Yes. Because you run Jentic One yourself, your own rules decide which Mitigant operations the agent may call and which credentials it may use. Since Mitigant carries scan and finding ids in the URL path (GET /scans/{scanId}, GET /findings/{findingId}), you can pin the agent to read-only posture work, letting it list cloud accounts, list assets, list findings, and inspect a single scan. Write actions such as triggering a new scan via POST /scans or starting an attack simulation are excluded unless you explicitly add them.

Mitigant Cloud Security API

Name: Mitigant Cloud Security API
Brand: Mitigant Cloud Security API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticSecurityVulnerability Managementbearer20 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Manage cloud accounts, run security scans, list findings and assets, and trigger attack simulations across AWS, Azure, and GCP through the Mitigant cloud security platform.

Use for: I want to connect a new AWS account to Mitigant, Trigger a security scan on a connected cloud account, List all critical findings for a specific cloud account, Retrieve the asset inventory discovered by the latest scan

Not supported: Does not handle endpoint detection, application code scanning, or SIEM event ingestion - use for cloud account posture, findings, assets, and attack simulation only.

Jentic publishes the only available OpenAPI specification for Mitigant Cloud Security API, keeping it validated and agent-ready. Mitigant (formerly Resility) is a cloud infrastructure security platform that runs attack surface management, cloud security posture assessment, and chaos-style attack simulations across AWS, Azure, and GCP environments. The API exposes 20 endpoints for managing cloud accounts, scans, findings, assets, attack simulations, dashboard metrics, and compliance reports - designed for embedding cloud security checks into automation pipelines.

Jentic One on Github View OpenAPI Document