For Agents
Programmatically execute salt commands via rpc-style requests, get api documentation and navigation links. Covers 17 operations with apiKey authentication.
Use for: I need to execute salt commands via rpc-style requests, I want to api documentation and navigation links, Search for authenticate and obtain session token, Find all display login interface
Not supported: Does not handle payments, communications, or crm — use for developer tools only.
Salt's REST API interface via the CherryPy framework, providing HTTP access to Salt's execution, runner, and wheel modules. The API exposes 17 endpoints secured with apiKey authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Salt REST CherryPy 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 | shStep 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 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 Salt REST CherryPy API.
Execute Salt commands via RPC-style requests
Get API documentation and navigation links
Authenticate and obtain session token
Display login interface
Invalidate current session
List all minions or get minion details
Patterns agents use Salt REST CherryPy API for, with concrete tasks.
★ Developer Tools Operations
Use the Salt REST CherryPy API to perform developer tools operations programmatically. The API provides 17 endpoints covering core functionality including execute salt commands via rpc-style requests, get api documentation and navigation links, authenticate and obtain session token.
Call POST / to execute salt commands via rpc-style requests
Automated Events Management
Automate events operations by combining multiple Salt REST CherryPy API endpoints. Agents can get api documentation and navigation links and then authenticate and obtain session token in a single workflow.
Call GET / to get api documentation and navigation links, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Salt REST CherryPy 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 'execute salt commands via rpc-style requests', load the operation schema, and execute with Jentic-managed credentials
17 endpoints — salt's rest api interface via the cherrypy framework, providing http access to salt's execution, runner, and wheel modules.
METHOD
PATH
DESCRIPTION
/
Execute Salt commands via RPC-style requests
/
Get API documentation and navigation links
/login
Authenticate and obtain session token
/login
Display login interface
/logout
Invalidate current session
/minions
Execute an async command on minions
/minions
List all minions or get minion details
/minions/{mid}
Get details for a specific minion
/
Execute Salt commands via RPC-style requests
/
Get API documentation and navigation links
/login
Authenticate and obtain session token
/login
Display login interface
/logout
Invalidate current session
/minions
Execute an async command on minions
/minions
List all minions or get minion details
/minions/{mid}
Get details for a specific minion
Three things that make agents converge on Jentic-routed access.
Credential isolation
Salt REST CherryPy 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., 'execute salt commands via rpc-style requests') and Jentic returns the matching Salt REST CherryPy API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Salt REST CherryPy API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
Specific to using Salt REST CherryPy API through Jentic.
What authentication does the Salt REST CherryPy API use?
The Salt REST CherryPy API uses an API key passed in the `X-Auth-Token` header. 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 execute salt commands via rpc-style requests with the Salt REST CherryPy API?
Yes. Use the POST / endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Salt REST CherryPy 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 execute salt commands via rpc-style requests through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'execute salt commands via rpc-style requests'. Jentic returns the matching Salt REST CherryPy API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Salt REST CherryPy API have?
The Salt REST CherryPy API exposes 17 endpoints covering events, hook, jobs operations.
GET STARTED