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

# Rancher Manager API

Rancher Manager v3 API for managing Kubernetes clusters, projects, workloads, authentication, and infrastructure resources. The API exposes 354 endpoints secured with basic, bearer authentication.

## For AI agents

Programmatically create cluster, list clusters. Covers 354 operations with basic, bearer authentication.

## Scope

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

## Capabilities

- Create Cluster
- List Clusters
- Get Cluster
- Update Cluster
- Delete Cluster
- generateKubeconfig action on Cluster
- importYaml action on Cluster

## Use cases

### Cloud Infrastructure Operations

Use the Rancher Manager API to perform cloud infrastructure operations programmatically. The API provides 354 endpoints covering core functionality including create cluster, list clusters, get cluster.

Example prompt: Call POST /clusters to create cluster

### Automated Clusters Management

Automate clusters operations by combining multiple Rancher Manager API endpoints. Agents can list clusters and then get cluster in a single workflow.

Example prompt: Call GET /clusters to list clusters, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Rancher Manager 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 basic, bearer tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /clusters | Create Cluster |
| GET | /clusters | List Clusters |
| GET | /clusters/{id} | Get Cluster |
| PUT | /clusters/{id} | Update Cluster |
| DELETE | /clusters/{id} | Delete Cluster |
| POST | /clusters/{id}?action=generateKubeconfig | generateKubeconfig action on Cluster |
| POST | /clusters/{id}?action=importYaml | importYaml action on Cluster |
| POST | /clusters/{id}?action=exportYaml | exportYaml action on Cluster |

## Key resources

- **Clusters** — Cluster management
- **Nodes** — Node management
- **Projects** — Project management
- **Auth** — Authentication and authorization
- **AuthConfig** — Auth provider configuration

## Why Jentic

- **Setup:** Wiring the Rancher Manager API by hand means learning both its basic and bearer auth, pointing every call at your own rancher_host, and hand-coding requests across hundreds of cluster and node endpoints. Through Jentic you install once, import the Rancher Manager API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Rancher puts the cluster id in the URL path (/clusters/{id}), so a rule can pin your agent to one cluster: it can read and update that cluster and nothing else. You choose the operations it may call, so destructive ones like deleting a cluster or generating a kubeconfig are not included unless you add them.
- **Credential handling:** Your Rancher 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 'list managed clusters' or 'create a cluster', and Jentic returns the matching Rancher operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Amazonaws** — Alternative cloud infrastructure API
- **Azure** — Alternative cloud infrastructure API
- **Googleapis** — Complementary cloud infrastructure API
- **Digitalocean** — Complementary cloud infrastructure API

## FAQ

### What authentication does the Rancher Manager API use?

The Rancher Manager API uses basic, bearer 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 create cluster with the Rancher Manager API?

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

### What are the rate limits for the Rancher Manager 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 create cluster through Jentic?

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

### How many endpoints does the Rancher Manager API have?

The Rancher Manager API exposes 354 endpoints covering clusters, nodes, projects operations.

### Can I limit what my agent is allowed to do with the Rancher Manager API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Rancher Manager operations and credentials the agent may use. Because Rancher puts the cluster id in the URL path (/clusters/{id}), a rule can pin the agent to a single cluster and let it only read and update that one. You also pick the operations it may call, so destructive actions like deleting a cluster or generating a kubeconfig are excluded unless you add them.