Endor Labs AppSec API
66
AI ReadinessAI-Aware (B)66/100
Agent-ready OpenAPI document · curated by JenticSecurityVulnerability Managementbearer5 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
List projects, vulnerabilities, and packages, trigger scans, and check policies in an Endor Labs namespace for software supply chain security workflows.
Use for: I need to list all vulnerabilities in my Endor Labs namespace, Find every project under the 'platform' namespace, Trigger a new dependency scan on a specific project, Retrieve all packages affected by a critical CVE
Not supported: Does not handle source code repository management, secret scanning, or runtime workload protection - use for software supply chain vulnerability management, dependency scanning, and policy enforcement only.
Jentic publishes the only available OpenAPI specification for Endor Labs AppSec API, keeping it validated and agent-ready. Endor Labs is an application security platform focused on software supply chain risk; the API exposes namespace-scoped projects, findings, packages, scans, and policies. Security teams use it to enumerate vulnerabilities across repositories, kick off scans on demand, and check policy compliance. Each operation is namespaced, so multi-tenant CI integrations can isolate results per team or business unit.
Install Jentic One Beta
Connect the Endor Labs AppSec API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Endor Labs AppSec 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.
1
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%2Fendorlabs.com%2Fendorlabs" | sh2
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%2Fendorlabs.com%2Fendorlabs" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Endor Labs AppSec API.
Enumerate projects within an Endor Labs namespace for inventory checks
List vulnerability findings filtered by namespace for triage
Look up packages and their dependency graph metadata
Trigger a fresh scan against a project or repository
List active security policies enforced in a namespace
Use Cases
Patterns agents use Endor Labs AppSec API for, with concrete tasks.
★ Daily Vulnerability Triage
Pull the day's findings via GET /v1/namespaces/{namespace}/findings, filter by severity, and route critical issues to the right team. Endor Labs reports findings against the resolved dependency graph, so agents can ground triage in real call-path reachability rather than raw CVE lists. Most security teams run this kind of report once per workday.
List all findings in namespace 'prod' with severity 'CRITICAL' from the last 24 hours and post a summary to Slack
On-Demand Scan from CI
Call POST /v1/namespaces/{namespace}/scans from a CI job to scan a freshly merged commit, then poll findings to fail the build on critical issues. This shifts security left without baking the scanner into every pipeline image.
POST a scan request for project 'svc-checkout' in namespace 'prod' and return the scan ID
Project and Policy Inventory
Combine GET /v1/namespaces/{namespace}/projects and GET /v1/namespaces/{namespace}/policies to produce a one-shot view of what is being scanned and which guardrails are enforced. Useful for security architects auditing coverage across business units.
List every project and active policy in namespace 'security' and flag projects with no policy attached
Agent-Driven AppSec Investigation
An agent receives a CVE alert, searches Jentic for 'find packages affected by a CVE', loads the Endor Labs packages operation, and returns the impacted projects. This compresses what was a multi-tab investigation into a single agent turn.
Given CVE-2025-1234, list packages in namespace 'prod' that are affected and return their parent projects
Key Endpoints
5 endpoints — jentic publishes the only available openapi specification for endor labs appsec api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/v1/namespaces/{namespace}/projects
List projects in a namespace
GET
/v1/namespaces/{namespace}/findings
List vulnerability findings
GET
/v1/namespaces/{namespace}/packages
List packages
POST
/v1/namespaces/{namespace}/scans
Create a scan
GET
/v1/namespaces/{namespace}/policies
List policies
GET
/v1/namespaces/{namespace}/projects
List projects in a namespace
GET
/v1/namespaces/{namespace}/findings
List vulnerability findings
GET
/v1/namespaces/{namespace}/packages
List packages
POST
/v1/namespaces/{namespace}/scans
Create a scan
GET
/v1/namespaces/{namespace}/policies
List policies
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
E
Endor Labs AppSec API
- AI-Aware (B)66/100
84
Foundational Compliance63
Developer Experience & Jentic Compatibility46
AI-Readiness & Agent Experience94
Agent Usability60
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
84
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
35%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
46
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
33%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Endor Labs AppSec API by hand means handling its bearer auth, threading your namespace through every route, and building your own error handling against https://api.endorlabs.com. Through Jentic you install once, import the Endor Labs AppSec API from the API Directory, store the token once, and your agent calls it.
Permission scoping
The Endor Labs AppSec API puts the namespace in the URL path (/v1/namespaces/{namespace}/...), so a rule can pin your agent to one namespace: it can read that namespace's projects, findings, packages, and policies and nothing else. You choose the operations it may call, so triggering a scan is not included unless you add it.
Credential isolation
Your Endor Labs 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 vulnerability findings in a namespace' or 'read dependency packages', and Jentic returns the matching Endor Labs operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Endor Labs AppSec API through Jentic.
Why is there no official OpenAPI spec for Endor Labs AppSec API?
Endor Labs does not publish a public OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Endor Labs AppSec 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 Endor Labs AppSec API use?
The API uses bearer-token authentication via the standard `Authorization: Bearer <token>` header. Through Jentic, the token is stored encrypted in the vault and never enters the agent's prompt context.
Can I trigger a scan from CI using the Endor Labs API?
Yes. POST /v1/namespaces/{namespace}/scans queues a scan against a project. CI jobs commonly call this endpoint after a merge and then poll findings before deciding to pass or fail the build.
How are results scoped in the Endor Labs API?
Every operation is scoped to a namespace via the path parameter `{namespace}`, so findings, packages, projects, and policies are isolated per tenant or business unit. The agent must supply the namespace on every call.
What are the rate limits for the Endor Labs AppSec API?
The spec does not declare rate limits. Endor Labs enforces per-tenant throttles in production; back off on HTTP 429 responses and confirm exact limits with your Endor Labs account team.
How do I list critical findings through Jentic?
Run `pip install jentic`, search 'list endor labs vulnerability findings', and Jentic returns GET /v1/namespaces/{namespace}/findings with its input schema. The agent supplies the namespace and severity filter, then executes against base URL https://api.endorlabs.com.
Can I limit what my agent is allowed to do with the Endor Labs AppSec API?
Yes. Because you run Jentic One yourself, your own rules decide which Endor Labs operations and credentials the agent may use. Every route carries the namespace in its path (/v1/namespaces/{namespace}/...), so you can pin the agent to a single namespace and let it read only that namespace's projects, findings, packages, and policies. You also choose the exact operations it may call, so triggering a scan via POST /v1/namespaces/{namespace}/scans stays off unless you explicitly allow it.
GET STARTED