canonical: https://jentic.com/apis/rumble.run/rumble-main

# Rumble Run Rumble API (deprecated)

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.

## For AI 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.

## Scope

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.

## Capabilities

- 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
- 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

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/org/assets` | Search assets |
| GET | `/org/assets/{asset_id}` | Get asset details |
| PUT | `/org/sites/{site_id}/scan` | Create a scan task for a site |
| GET | `/org/tasks/{task_id}` | Get task details |
| PATCH | `/org/assets/bulk/tags` | Update tags across assets by search |
| GET | `/export/org/assets.csv` | Export the asset inventory as CSV |
| GET | `/org/services` | List discovered services |
| PUT | `/org/sites/{site_id}/import/nessus` | Import a Nessus scan file |

## Key resources

- **Assets** — Search, view, tag, comment on, and remove discovered assets, plus top hardware, OS, tag, and type reports
- **Services and wireless** — Discovered services with subnet and protocol statistics, and wireless LANs
- **Sites and tasks** — Sites with scan creation and data import, and scan tasks with status, logs, change reports, and stop
- **Exports** — Asset, service, site, and wireless inventory as CSV, JSON, JSON lines, Nmap XML, and ServiceNow formats
- **Agents** — Scanning agents per organization, with site assignment, forced update, and removal
- **Account administration** — Organizations, users, groups, SSO group mappings, scan templates, credentials, API keys, and the event log

## AI readiness

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.

- **Score:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 89 / 100
  - Developer Experience & Jentic Compatibility: 74 / 100
  - AI-Readiness & Agent Experience: 45 / 100
  - Agent Usability: 80 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/rumble.run/rumble-main/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **runZero API** — The maintained successor to the Rumble API for asset discovery
- **Shodan API** — Internet-wide scan data on exposed hosts and services
- **Censys Search API** — Search internet hosts and certificates from Censys scans
- **ServiceNow API** — IT service management and CMDB

## FAQ

### 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.
