Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Rumble API (deprecated), 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%2Frumble.run%2Frumble-main" | shStep 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%2Frumble.run%2Frumble-main" | 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.
What an agent can do with Rumble API (deprecated) API.
Start a scan task for a site with PUT /org/sites/{site_id}/scan, setting targets, scan rate, and TCP ports
Search discovered assets with a query such as alive:true and os:windows and read each asset's details
Apply or clear tags across many assets at once using a search query
Export the asset inventory as CSV, JSON lines, Nmap-style XML, or ServiceNow CSV and JSON
GET STARTED
Sync the asset inventory incrementally from a created_at or updated_at checkpoint
Import Nessus or other scan data files into a site
Administer organizations, users, groups, SSO group mappings, and API key rotation
Patterns agents use Rumble API (deprecated) API for, with concrete tasks.
★ Network inventory agent through Jentic
A security engineer wants an agent that can answer questions about what is on the network. Through Jentic the agent searches for 'search network assets', receives the Rumble operation with its input schema, and calls GET /org/assets with a search query such as alive:true and os:windows. It can follow up with GET /org/assets/{asset_id} for details and GET /org/services to see what each host exposes, using the bearer token stored once in Jentic.
Call GET /org/assets with search 'alive:true and os:windows', then call GET /org/assets/{asset_id} for the first three results and summarise their addresses and operating systems
Scheduled discovery scans
Teams keep the inventory current by scanning each site on a schedule. PUT /org/sites/{site_id}/scan creates a scan task from ScanOptions, where targets is required and fields like rate, tcp-ports, scan-frequency, and scan-name shape the run. GET /org/tasks/{task_id} reports progress, POST /org/tasks/{task_id}/stop cancels a run, and GET /org/tasks/{task_id}/changes returns a temporary URL for the change report.
Call PUT /org/sites/{site_id}/scan with targets '10.0.0.0/24' and scan-name 'weekly-office', then poll GET /org/tasks/{task_id} until it completes and fetch GET /org/tasks/{task_id}/changes
Inventory export to CMDB and SIEM
Asset data often has to land in a CMDB or analytics tool. The export endpoints return the inventory as /export/org/assets.csv, /export/org/assets.jsonl, /export/org/assets.nmap.xml, or ServiceNow-shaped CSV and JSON, and the sync exports under /export/org/assets/sync/updated/assets.json take a since checkpoint so only changed assets are pulled on each run.
Call GET /export/org/assets/sync/updated/assets.json with since set to the last sync time, then push the returned assets to the CMDB
Bulk asset tagging
Tags let teams group assets by owner, location, or risk. PATCH /org/assets/bulk/tags applies tags to every asset matching a search query, with both search and tags required, and POST /org/assets/bulk/clearTags removes all tags from matching assets. PATCH /org/assets/{asset_id}/tags and PATCH /org/assets/{asset_id}/comments adjust a single asset.
Call PATCH /org/assets/bulk/tags with search 'alive:true and os:windows' and tags 'Owner=IT -Legacy', then confirm with GET /org/assets using the same search
116 endpoints — the rumble api drives rumble network discovery, the network asset inventory product now renamed runzero, and is frozen at version 2.
METHOD
PATH
DESCRIPTION
/org/assets
Search assets
/org/assets/{asset_id}
Get asset details
/org/sites/{site_id}/scan
Create a scan task for a site
/org/tasks/{task_id}
Get task details
/org/assets/bulk/tags
Update tags across assets by search
/export/org/assets.csv
Export the asset inventory as CSV
/org/services
List discovered services
/org/sites/{site_id}/import/nessus
Import a Nessus scan file
/org/assets
Search assets
/org/assets/{asset_id}
Get asset details
/org/sites/{site_id}/scan
Create a scan task for a site
/org/tasks/{task_id}
Get task details
/org/assets/bulk/tags
Update tags across assets by search
/export/org/assets.csv
Export the asset inventory as CSV
/org/services
List discovered services
/org/sites/{site_id}/import/nessus
Import a Nessus scan file
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Rumble by hand means sending a bearer token, choosing between an Organization Key and an Export Token for different endpoint groups, and handling exports that return CSV, JSON lines, or XML instead of plain JSON. Through Jentic you install once, import Rumble from the API Directory, store the token once, and your agent calls it.
Permission scoping
Rumble puts the site, asset, and task ids in the URL path (/org/sites/{site_id}, /org/assets/{asset_id}, /org/tasks/{task_id}), so a rule can pin your agent to one site's scan and import operations. You choose the operations it may call, so destructive ones like removing a site or rotating the API key are not included unless you add them.
Credential isolation
Your Rumble 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 'search network assets' or 'export the asset inventory', and Jentic returns the matching Rumble operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Rumble API (deprecated) API through Jentic.
What authentication does the Rumble API use?
The Rumble API declares an HTTP bearer scheme named bearerAuth in its OpenAPI spec, so calls send a key as a bearer token in the Authorization header. The spec's tags note that Organization endpoints require an Organization Key and Export endpoints accept an Export Token or Organization Key, while the Public endpoints, such as GET /releases/agent/version, are unauthenticated. Through Jentic the token is held by your own Jentic One instance and attached at call time.
Is the Rumble API still maintained?
No. The spec states that Rumble Network Discovery is now runZero and that this API is frozen and no longer updated as of version 2.15.0. It remains listed for existing integrations against the Rumble console; for new work, use the runZero API, which is also in the Jentic API Directory.
Can I export my asset inventory to ServiceNow with the Rumble API?
Yes. GET /export/org/assets.servicenow.csv and GET /export/org/assets.servicenow.json return the asset inventory shaped for ServiceNow, and GET /export/org/services.servicenow.csv does the same for services. For incremental loads, GET /export/org/assets/sync/updated/assets.json takes a since checkpoint.
What are the rate limits for the Rumble API?
The OpenAPI spec does not specify rate limits. Because the API is frozen, check the current runZero documentation at https://www.runzero.com for limits that apply to the console.
How do I start a network scan through Jentic?
Search Jentic for 'start a network scan', load the PUT /org/sites/{site_id}/scan operation, and execute it with the site id and a ScanOptions body whose targets field lists the ranges to scan. Track it with GET /org/tasks/{task_id}. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there a Rumble MCP server?
You don't need an MCP server to give your agent Rumble. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent discovers the asset, scan, and export operations it needs on demand, without loading every tool definition into its context.
Can I limit what my agent is allowed to do with the Rumble API?
Yes. For a read-only inventory assistant, write a rule that allows GET /org/assets, GET /org/assets/{asset_id}, and GET /org/services. The agent can answer questions about hosts and services but cannot start scans, remove sites, or rotate keys, and each call it makes is logged.
Know of an official OpenAPI document? Contribute it →
For Agents
Start Rumble network scans, query discovered assets and services, tag assets in bulk, and export the inventory to CSV, JSON, Nmap XML, or ServiceNow formats. The API is frozen at 2.15.0 and succeeded by runZero.
Use for: Start a network scan of 10.0.0.0/24 on my Rumble site, Find all Windows assets that are currently alive, Export my asset inventory as CSV for ServiceNow, I need to tag every asset matching a search query
Not supported: Does not patch hosts, score CVEs, or monitor internet-facing exposure from outside your network. Use for network asset discovery scans and inventory exports on the frozen Rumble console only.
The Rumble API drives Rumble Network Discovery, the network asset inventory product now renamed runZero, and is frozen at version 2.15.0. It starts scan tasks against a site's targets, imports scan data including Nessus files, and returns the discovered assets, services, and wireless LANs for an organization. Export endpoints deliver the asset and service inventory as CSV, JSON, JSON lines, Nmap-style XML, or ServiceNow-ready formats, and account endpoints administer organizations, users, groups, SSO group mappings, scan templates, and API keys.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
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>