canonical: https://jentic.com/apis/vmware.local/vmware-local

# Vmware vRealize Network Insight API Reference

vRealize Network Insight API Reference. The API exposes 161 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create an auth token, delete an auth token.. Covers 161 operations with apiKey authentication.

## Scope

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

## Capabilities

- Create an auth token
- Delete an auth token.
- List arista switch data sources
- Show arista switch data source details
- Update an arista switch data source

## Use cases

### Analytics Operations

Use the vRealize Network Insight API Reference to perform analytics operations programmatically. The API provides 161 endpoints covering core functionality including create an auth token, delete an auth token., create an arista switch data source.

Example prompt: Call POST `/auth/token` to create an auth token

### Automated Authentication Management

Automate authentication operations by combining multiple vRealize Network Insight API Reference endpoints. Agents can delete an auth token. and then create an arista switch data source in a single workflow.

Example prompt: Call DELETE `/auth/token` to delete an auth token., then verify the result

### AI Agent Integration via Jentic

AI agents discover and call vRealize Network Insight API Reference 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 apiKey tokens manually.

Example prompt: Search Jentic for 'create an auth token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/auth/token` | Create an auth token |
| DELETE | `/auth/token` | Delete an auth token. |
| POST | `/data-sources/arista-switches` | Create an arista switch data source |
| GET | `/data-sources/arista-switches` | List arista switch data sources |
| GET | `/data-sources/arista-switches/{id}` | Show arista switch data source details |
| PUT | `/data-sources/arista-switches/{id}` | Update an arista switch data source |
| DELETE | `/data-sources/arista-switches/{id}` | Delete an arista switch data source |
| POST | `/data-sources/arista-switches/{id}/disable` | Disable an arista switch data source |

## Key resources

- **Authentication** — Authentication APIs
- **Data Sources** — Data source APIs
- **Entities** — Entities APIs
- **Search** — Search APIs
- **Infrastructure** — Infra APIs

## Why Jentic

- **Setup:** Wiring vRealize Network Insight by hand means obtaining a token from `/auth/token`, setting it in the Authorization header against your own vRNI host, and managing data-source calls yourself. Through Jentic you install once, import vRealize Network Insight from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** vRealize Network Insight puts the data-source id in the URL path (`/data-sources/arista-switches/{id}`), so a rule can pin your agent to reading one data source. You choose the operations it may call, so destructive ones like data-source deletion or disable are not included unless you add them.
- **Credential handling:** Your vRealize Network Insight 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 'obtain an auth token' or 'list Arista switch data sources', and Jentic returns the matching vRealize Network Insight operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

### What authentication does the vRealize Network Insight API Reference use?

The vRealize Network Insight API Reference uses an API key passed in the `Authorization` header. 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 create an auth token with the vRealize Network Insight API Reference?

Yes. Use the POST `/auth/token` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the vRealize Network Insight API Reference?

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 create an auth token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create an auth token'. Jentic returns the matching vRealize Network Insight API Reference operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the vRealize Network Insight API Reference have?

The vRealize Network Insight API Reference exposes 161 endpoints covering authentication, data sources, entities operations.

### Can I limit what my agent is allowed to do with the vRealize Network Insight API?

Yes. Because you self-host Jentic One, your own rules decide which vRealize Network Insight operations and credentials the agent may use. Since the data-source id sits in the URL path, such as `/data-sources/arista-switches/{id}`, you can pin the agent to reading a single data source, and you choose the exact operations it may call. That means destructive calls like deleting or disabling a data source are excluded unless you explicitly add them.