Rapid7 VM API

Name: Rapid7 VM API
Brand: Rapid7 VM API
Availability: InStock

✓ Official Vendor SpecCRMCustomer Supportbasic330 EndpointsREST

For Agents

Programmatically resources, console commands. Covers 330 operations with basic authentication.

Install Jentic One Beta

Connect the Rapid7 VM API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Rapid7 VM 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://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 Rapid7 VM API.

Resources

Console Commands

Information

License

GET STARTED

Start building with Rapid7 VM API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Rapid7 VM API for, with concrete tasks.

★ CRM Operations

Use the Rapid7 VM API to perform crm operations programmatically. The API provides 330 endpoints covering core functionality including resources, console commands, information.

Call GET /api/3 to resources

Automated Root Management

Automate root operations by combining multiple Rapid7 VM API endpoints. Agents can console commands and then information in a single workflow.

Call POST /api/3/administration/commands to console commands, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Rapid7 VM API 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 basic tokens manually.

Search Jentic for 'resources', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

330 endpoints — overview this guide documents the rapid7 vm application programming interface (api) version 3.

METHOD

PATH

DESCRIPTION

GET

/api/3

Resources

POST

/api/3/administration/commands

Console Commands

GET

/api/3/administration/info

Information

POST

/api/3/administration/license

License

GET

/api/3/administration/license

License

GET

/api/3/administration/logs

Logs

GET

/api/3/administration/properties

Properties

GET

/api/3/administration/settings

Settings

GET

/api/3

Resources

POST

/api/3/administration/commands

Console Commands

GET

/api/3/administration/info

Information

POST

/api/3/administration/license

License

GET

/api/3/administration/license

License

GET

Why Jentic?

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

Credential isolation

Your Rapid7 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 'list scanned assets' or 'get scan results', and Jentic returns the matching Rapid7 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 Rapid7 VM API through Jentic.

What authentication does the Rapid7 VM API use?

The Rapid7 VM API uses HTTP Basic authentication. 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 resources with the Rapid7 VM API?

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

What are the rate limits for the Rapid7 VM API?

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 resources through Jentic?

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

How many endpoints does the Rapid7 VM API have?

The Rapid7 VM API exposes 330 endpoints covering root, asset, asset discovery operations.

Can I limit what my agent is allowed to do with the Rapid7 VM API?

Yes. Because you run Jentic One yourself, your own rules decide which Rapid7 operations and credentials the agent may use. Rapid7 puts resource ids in the URL path across its asset and scan endpoints, so you can pin the agent to a single asset or scan rather than the whole console. You also choose which operations it may call, so destructive ones like posting administration commands or updating the license stay off limits unless you explicitly add them.

Rapid7 VM API

Connect the Rapid7 VM API to your agent

Capabilities

Start building with Rapid7 VM API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs