canonical: https://jentic.com/apis/runzero.com/runzero

# runZero API

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.

## For AI agents

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

## Scope

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

## Capabilities

- 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

## Use cases

### Communications Operations

Use the runZero API to perform communications operations programmatically. The API provides 181 endpoints covering core functionality including returns latest agent version, returns latest scanner version, returns latest platform version.

Example prompt: Call GET `/releases/agent/version` to returns latest agent version

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

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

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

## Key endpoints

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

## Key resources

- **Account** — Requires Account key (starts with CT), or OAuth
- **Organization** — Requires Organization key (starts with OT), Account key (starts with CT), or OAuth
- **Export** — Requires Export token (starts with ET), Organization key (starts with OT), Account key (starts with
- **Import** — Requires Organization key (starts with OT), Account key (starts with CT), or OAuth
- **Public** — Unauthenticated

## Why Jentic

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

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

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