canonical: https://jentic.com/apis/autobahn-security.com/autobahn-security # Autobahn Security Autobahn External API The Autobahn Security API is the platform's external REST interface for its vulnerability management workflow. After the auth endpoint issues a token, the API reads assets and their port details, security issues and knowledge-base entries, and scan results, targets, and metadata, and it manages team members and asset and issue tags. Only the auth endpoint requires no token; the others use a bearer token. ## For AI agents Lets an AI agent read Autobahn Security assets, issues, and scan results and manage tags and team members after obtaining a bearer token. ## Scope Reads and manages data within the Autobahn Security platform only; it does not run its own scans on demand or cover assets outside the platform, so pair it with a scanner for those needs. ## Capabilities - Obtain a bearer token from the auth endpoint - List assets and read their port details - Read security issues and knowledge-base entries - Read scan results, targets, ports, and metadata - Assign and remove tags and assignees on assets and issues - Manage team members and invitations ## Use cases ### Pull vulnerability data into a dashboard Security teams centralize findings from many tools. The Autobahn Security API reads assets, issues, and scan results, so an integration can feed live vulnerability data into a dashboard or a risk report without exporting from the UI. Example prompt: Read the current issues and summarize how many are open by severity. ### Automate asset and issue triage Triage means labelling and assigning findings as they arrive. The API adds and removes tags and assignees on assets and issues, so an integration can route a new finding to the right owner and tag it for tracking automatically. Example prompt: Tag a given asset and assign its open issues to the responsible owner. ### Track scan coverage and metadata Knowing what has been scanned matters as much as the findings. The API reads scans, their targets, ports, and metadata, so an integration can confirm coverage and report on scan history across the estate. Example prompt: List recent scans and report their targets and completion metadata. ### Let an agent answer security questions An AI agent supporting a security team can obtain a token and read assets, issues, and scans on request. Through Jentic the agent discovers these operations by intent and runs them under the team's own token, keeping actions within the team's controls. Example prompt: Given an asset name, read its open issues and report them to the user. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/api/external/auth` | Obtain a bearer token | | POST | `/api/external/assets` | List assets | | POST | `/api/external/issues` | List security issues | | POST | `/api/external/scans` | List scans and their results | | POST | `/api/external/issues/kb` | Read issue knowledge-base entries | | POST | `/api/external/teams/members` | List team members | ## Key resources - **Auth** — Issues the bearer token used by the other operations - **Assets** — Tracked assets and their port details - **Issues** — Security issues and knowledge-base entries - **Scans** — Scan results, targets, ports, and metadata - **Teams** — Team members and invitations ## Why Jentic - **Setup:** Wiring Autobahn Security into an agent yourself means calling the auth endpoint, holding the returned token, and mapping the asset, issue, and scan reads. With Jentic you install once, import Autobahn Security from the Directory, and store the credential a single time. - **Permission scoping:** Running Jentic in your own instance, you decide which Autobahn Security operations the agent may call, so you can allow reads of assets and issues while blocking tag or team changes. Access is granted per operation. - **Credential handling:** Your Autobahn Security credential is held encrypted by your own Jentic One instance and injected only when an operation runs, so it never appears in the agent's prompt, logs, or context. - **Discovery method:** Agents find Autobahn Security through Jentic's intent search: a request like read open issues for an asset resolves to the right operation with inputs and auth prepared. ## Related APIs - **Tenable Nessus** — Runs vulnerability scans and reports findings across assets. - **Tenable Attack Surface Management** — Discovers and monitors an organization's external attack surface. - **Contrast Security** — Detects vulnerabilities from inside running applications. ## FAQ ### Is there an MCP server for the Autobahn Security API? You do not need a dedicated MCP server. Through Jentic your self-hosted agent can call Autobahn Security operations directly by intent, so you connect the API without maintaining separate MCP tooling. ### Can I control what my agent is allowed to do in Autobahn Security? Yes. Because you run Jentic yourself, you choose which Autobahn Security operations your agent can call, so you can allow reads of assets and issues while withholding tag or team changes. Scoping is applied per operation. ### What authentication does the Autobahn Security API use? The auth endpoint issues a bearer token, and the other operations send that token in the Authorization header. Jentic obtains and injects the token from your stored credential when a call runs. ### What security data can the API read? It reads assets and their port details, security issues and knowledge-base entries, and scan results, targets, ports, and metadata, so you can build reporting and triage on top of it. ### Can the API modify tags and assignees? Yes. Alongside reads, it adds and removes tags and assignees on assets and issues and manages team members, so you can automate triage as well as reporting. ### How does an agent find Autobahn Security operations in Jentic? The agent searches Jentic by intent, such as reading open issues for an asset, and Jentic returns the matching operations ready to run under your token.