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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsaltproject.io%2Fsaltproject" | 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%2Fsaltproject.io%2Fsaltproject" | 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
GET STARTED
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
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Salt REST CherryPy API by hand means logging in for an X-Auth-Token, pointing requests at your own saltmaster host and port, and handling session expiry and retries yourself. Through Jentic you install once, import Salt from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
Salt puts the minion id in the URL path (/minions/{mid}), so a rule can pin your agent to specific minions: it can read the ones you allow and nothing else. You choose the operations it may call, so command execution like posting to the run endpoint is not included unless you add it.
Credential isolation
Your Salt credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list minions' or 'get minion details', and Jentic returns the matching Salt 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 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.
Can I limit what my agent is allowed to do with the Salt REST CherryPy API?
Yes. Jentic One is self-hosted by you, so your own rules decide which Salt operations and credentials the agent may use. Because Salt puts the minion id in the URL path (/minions/{mid}), you can pin the agent to specific minions so it reads only the ones you allow and nothing else. You choose the operations it may call, so command execution such as posting to the run endpoint is excluded unless you add it.
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.
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>