runZero API

Name: runZero API
Brand: runZero API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsVoice Telephonybearer, oauth2181 EndpointsREST

For Agents

Programmatically returns latest agent version, returns latest scanner version. Covers 181 operations with bearer, oauth2 authentication.

Use for: I need to returns latest agent version, I want to returns latest scanner version, Search for returns latest platform version, Find all returns a health check status (cloud and self-hosted)

Not supported: Does not handle payments, crm, or developer tools - use for communications only.

runZero API. API use is rate limited, you can make as many calls per day as you have licensed assets. The API exposes 181 endpoints secured with bearer, oauth2 authentication.

Jentic One on Github View OpenAPI Document

Install Jentic One Beta

Connect the runZero API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the runZero 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Frunzero.com%2Frunzero" | 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%2Frunzero.com%2Frunzero" | 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 runZero API.

Returns latest agent version

Import assets described by a registered custom integration

Exports the asset inventory

Asset inventory as JSON line-delimited

Monitor runZero API operational status and events

GET STARTED

Start building with runZero API

Explore with Jentic One

View OpenAPI Document

Automated Account Management

Automate account operations by combining multiple runZero API endpoints. Agents can returns latest scanner version and then returns latest platform version in a single workflow.

Call GET /releases/scanner/version to returns latest scanner version, then verify the result

AI Agent Integration via Jentic

AI agents discover and call runZero 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 bearer, oauth2 tokens manually.

Search Jentic for 'returns latest agent version', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

181 endpoints — runzero api.

METHOD

PATH

DESCRIPTION

GET

/releases/agent/version

Returns latest agent version

GET

/releases/scanner/version

Returns latest scanner version

GET

/releases/platform/version

Returns latest platform version

GET

/health

Returns a health check status (cloud and self-hosted)

POST

/import/org/{orgID}/assets

Import assets described by a registered custom integration

GET

/export/org/assets.json

Exports the asset inventory

GET

/export/org/assets.jsonl

Asset inventory as JSON line-delimited

GET

/export/org/assets.csv

Asset inventory as CSV

GET

/releases/agent/version

Returns latest agent version

GET

/releases/scanner/version

Returns latest scanner version

GET

/releases/platform/version

Returns latest platform version

GET

/health

Returns a health check status (cloud and self-hosted)

POST

/import/org/{orgID}/assets

Import assets described by a registered custom integration

GET

/export/org/assets.json

Exports the asset inventory

GET

/export/org/assets.jsonl

Asset inventory as JSON line-delimited

GET

/export/org/assets.csv

Asset inventory as CSV

Why Jentic?

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

Setup

Wiring the runZero API by hand means handling its bearer token or OAuth2 flow, pointing at console.runzero.com, and managing your own retries. Through Jentic you install once, import the runZero API from the API Directory, store the token once, and your agent calls it.

Permission scoping

runZero puts the org id in the URL path (/import/org/{orgID}/assets), so a rule can pin your agent to one org for imports. You choose the operations it may call, so you can allow read-only checks like version and health without granting asset imports unless you add them.

Credential isolation

Your runZero API 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 'get the latest agent version' or 'export org assets', and Jentic returns the matching runZero operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using runZero API through Jentic.

What authentication does the runZero API use?

The runZero API uses bearer, oauth2 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 returns latest agent version with the runZero API?

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

What are the rate limits for the runZero 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 returns latest agent version through Jentic?

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

How many endpoints does the runZero API have?

The runZero API exposes 181 endpoints covering account, organization, export operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which runZero operations and credentials your agent may use. Because runZero puts the org id in the URL path, such as /import/org/{orgID}/assets, you can pin the agent to a single organization for imports. You can also allow read-only calls like GET /health and GET /releases/agent/version while withholding asset imports and exports unless you explicitly grant them.

runZero API

Connect the runZero API to your agent

Capabilities

Start building with runZero API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs