Install Jentic One Beta
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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fproxmox.com%2Fproxmox" | shStep 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%2Fproxmox.com%2Fproxmox" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Proxmox VE API.
Create authentication ticket
Get API index
List cluster nodes
Start a virtual machine
Patterns agents use Proxmox VE API for, with concrete tasks.
★ Cloud Infrastructure Operations
GET STARTED
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
16 endpoints — proxmox ve uses a rest-like api for managing virtual machines, containers, storage, networking, clusters, and access control.
METHOD
PATH
DESCRIPTION
/access/ticket
Create authentication ticket
/
Get API index
/version
Get Proxmox VE version
/nodes
List cluster nodes
/nodes/{node}/qemu
Create a virtual machine
/nodes/{node}/qemu
List virtual machines
/nodes/{node}/qemu/{vmid}/status/start
Start a virtual machine
/nodes/{node}/qemu/{vmid}/status/stop
Stop a virtual machine
/access/ticket
Create authentication ticket
/
Get API index
/version
Get Proxmox VE version
/nodes
List cluster nodes
/nodes/{node}/qemu
Create a virtual machine
/nodes/{node}/qemu
List virtual machines
/nodes/{node}/qemu/{vmid}/status/start
Start a virtual machine
/nodes/{node}/qemu/{vmid}/status/stop
Stop a virtual machine
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Proxmox VE API by hand means obtaining an access ticket, sending the API token in the Authorization header, and targeting your own host and node names yourself. Through Jentic you install once, import Proxmox VE from the API Directory, store the token once, and your agent calls it.
Permission scoping
Proxmox puts the node and VM id in the URL path (/nodes/{node}/qemu/{vmid}/...), so a rule can pin your agent to one node or virtual machine. You choose the operations it may call, so state changes like stopping a VM are not included unless you add them.
Credential isolation
Your Proxmox VE 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 'list nodes' or 'start a virtual machine', and Jentic returns the matching Proxmox operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.
Can I limit what my agent is allowed to do with the Proxmox VE API?
Yes. Jentic One runs on your own infrastructure, so your rules decide which Proxmox VE operations and credentials the agent may use. Because Proxmox puts the node and VM id in the URL path (/nodes/{node}/qemu/{vmid}/...), you can pin the agent to a single node or virtual machine. You also choose exactly which operations it can call, so state changes such as stopping a VM via POST /nodes/{node}/qemu/{vmid}/status/stop are excluded unless you grant them.
For Agents
Programmatically create authentication ticket, get API index. Covers 16 operations with apiKey authentication.
Use for: I need to authentication ticket, I want to API index, Search for proxmox ve version, Find all cluster nodes
Not supported: Does not handle payments, communications, or crm - use for cloud infrastructure only.
Proxmox VE uses a REST-like API for managing virtual machines, containers, storage, networking, clusters, and access control. The API supports JSON as the primary data format and uses JSON Schema for formal definition. The API exposes 16 endpoints secured with apiKey authentication.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>