Versioneye API V1

Name: API V1 API
Brand: API V1
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource ControlapiKey3 EndpointsREST

For Agents

Programmatically retrieves all scans, retrieves a project scan result. Covers 3 operations with apiKey authentication.

Install Jentic One Beta

Connect the API V1 to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API V1, 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%2Fversioneye.com%2Fversioneye" | 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%2Fversioneye.com%2Fversioneye" | 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 API V1 API.

Retrieves all scans

Manage developer tools data programmatically

Integrate API V1 into automated workflows

Query and filter API V1 records by parameters

GET STARTED

Start building with API V1 API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use API V1 API for, with concrete tasks.

★ Developer Tools Operations

Use the API V1 to perform developer tools operations programmatically. The API provides 3 endpoints covering core functionality including retrieves all scans, retrieves a project scan result, retrieves a file object, containing information about dependencies in the file.

Call GET /api/v1/scans to retrieves all scans

Automated Scans Management

Automate scans operations by combining multiple API V1 endpoints. Agents can retrieves a project scan result and then retrieves a file object, containing information about dependencies in the file in a single workflow.

Call GET /api/v1/scans/{id} to retrieves a project scan result, then verify the result

AI Agent Integration via Jentic

AI agents discover and call API V1 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 'retrieves all scans', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

3 endpoints — versioneye.

METHOD

PATH

DESCRIPTION

GET

/api/v1/scans

Retrieves all scans

GET

/api/v1/scans/{id}

Retrieves a project scan result

GET

/api/v1/scans/{id}/files/{file_id}

Retrieves a file object, containing information about dependencies in the file

GET

/api/v1/scans

Retrieves all scans

GET

/api/v1/scans/{id}

Retrieves a project scan result

GET

/api/v1/scans/{id}/files/{file_id}

Retrieves a file object, containing information about dependencies in the file

Why Jentic?

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

Setup

Wiring the VersionEye API V1 by hand means passing its apiKey header, pointing at your configured host, and coding each scan and file lookup yourself. Through Jentic you install once, import the API V1 from the API Directory, store the key once, and your agent calls it.

Permission scoping

VersionEye puts the scan id in the URL path (/api/v1/scans/{id}) and is read-only, so a rule can pin your agent to reading one scan and its files. You choose the operations it may call, and only those reads run.

Credential isolation

Your VersionEye 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 'retrieve all scans' or 'get files for a scan', and Jentic returns the matching API V1 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.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using API V1 API through Jentic.

What authentication does the API V1 use?

The API V1 uses an API key passed in the `apiKey` 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 retrieves all scans with the API V1?

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

What are the rate limits for the API V1?

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 retrieves all scans through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'retrieves all scans'. Jentic returns the matching API V1 operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the API V1 have?

The API V1 exposes 3 endpoints covering scans operations.