Proxmox VE API

Name: Proxmox VE API
Brand: Proxmox VE API
Availability: InStock

✓ Official Vendor SpecCloud InfrastructureNetworkingapiKey16 EndpointsREST

For Agents

Programmatically create authentication ticket, get api index. Covers 16 operations with apiKey authentication.

Install Jentic One Beta

Connect the Proxmox VE API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Proxmox VE 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Proxmox VE API.

Create authentication ticket

Get API index

List cluster nodes

Start a virtual machine

GET STARTED

Start building with Proxmox VE API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Proxmox VE API for, with concrete tasks.

★ Cloud Infrastructure Operations

Use the Proxmox VE API to perform cloud infrastructure operations programmatically. The API provides 16 endpoints covering core functionality including create authentication ticket, get api index, get proxmox ve version.

Call POST /access/ticket to create authentication ticket

Automated Access Management

Automate access operations by combining multiple Proxmox VE API endpoints. Agents can get api index and then get proxmox ve version in a single workflow.

Call GET / to get api index, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Proxmox VE 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 apiKey tokens manually.

Search Jentic for 'create authentication ticket', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

16 endpoints — proxmox ve uses a rest-like api for managing virtual machines, containers, storage, networking, clusters, and access control.

METHOD

PATH

DESCRIPTION

POST

/access/ticket

Create authentication ticket

GET

Get API index

GET

/version

Get Proxmox VE version

GET

/nodes

List cluster nodes

POST

/nodes/{node}/qemu

Create a virtual machine

GET

/nodes/{node}/qemu

List virtual machines

POST

/nodes/{node}/qemu/{vmid}/status/start

Start a virtual machine

POST

/nodes/{node}/qemu/{vmid}/status/stop

Stop a virtual machine

POST

/access/ticket

Create authentication ticket

GET

Get API index

GET

/version

Get Proxmox VE version

GET

/nodes

List cluster nodes

POST

/nodes/{node}/qemu

Create a virtual machine

GET

/nodes/{node}/qemu

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Proxmox VE API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'create authentication ticket') and Jentic returns the matching Proxmox VE API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Proxmox VE API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Proxmox VE API through Jentic.

What authentication does the Proxmox VE API use?

The Proxmox VE API uses an API key passed in the `PVEAuthCookie` cookie. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I create authentication ticket with the Proxmox VE API?

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

What are the rate limits for the Proxmox VE 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 authentication ticket through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'create authentication ticket'. Jentic returns the matching Proxmox VE API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Proxmox VE API have?

The Proxmox VE API exposes 16 endpoints covering access, cluster, nodes operations.

Proxmox VE API

Connect the Proxmox VE API to your agent

Capabilities

Start building with Proxmox VE API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs