CyberArk APIs for AI Agents
SecuritySecrets ManagementJentic-Generated SpecsAPI keybasic, apiKeyAgent Ready
CyberArk API Catalog
2 APIs across 1 product group.
Security2
CyberArk Conjur APIStore and retrieve secrets, create access policies, and list roles in CyberArk Conjur via four core REST endpoints.~4 endpointsConjurProgrammatically authenticate to Conjur, retrieve and store secrets, manage policies and roles, and authorise workloads via API key or Kubernetes mutual TLS.~0 endpoints
Which CyberArk API should I use?
| I want to... | Use | Why |
|---|---|---|
| Store, retrieve, create a policy, and list roles with the minimum surface | CyberArk Conjur API | The curated four-endpoint spec covers POST /secrets, GET /secrets/{id}, POST /policies, and GET /roles and nothing else, which keeps integrations simple. |
| Authentication flows, host factory enrolment, or certificate authority operations | Conjur | The fuller Conjur spec adds login and API-key authentication, Kubernetes mutual TLS, host factory tokens, public keys, resources, status, and certificate authority surfaces. |
Install Jentic One Beta
Connect the CyberArk APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CyberArk APIs, 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.
1
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%2Fcyberark.com" | sh2
Step 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%2Fcyberark.com" | 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.
Once connected, ask your agent something like: “manage CyberArk Conjur secrets and access policies”.
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Conjur specs by hand means handling API-key, basic-auth, or Kubernetes mutual-TLS authentication, targeting the right Conjur appliance, and mapping the secret, policy, and role routes yourself. Through Jentic you install Jentic One once, add either Conjur API from the Jentic directory, store the credentials once, and your agent calls both.
Permission scoping
Your own rules decide which Conjur operations the agent may call across both specs. Because the compact spec puts the secret id in the URL path, a rule can pin an agent to reading one specific secret, and writing secrets or applying policies stays out unless you add them.
Credential isolation
Your Conjur API keys and basic-auth credentials are stored once, encrypted, by your own Jentic One instance, which performs the Conjur authentication step at execution time. The long-lived secret never enters the agent's prompt, logs, or context.
FAQs
Specific to using CyberArk APIs through Jentic.
What can an AI agent do across the CyberArk Conjur APIs?
An agent can authenticate a workload, retrieve and store secrets at runtime, load and update policy-as-code definitions, and enumerate roles in the policy graph. The compact spec covers the four core secret, policy, and role operations, while the fuller spec adds authentication flows, host factory enrolment, and certificate authority surfaces.
Why does Jentic publish two Conjur specifications?
The two specs serve different needs against the same platform. The four-endpoint spec is a leaner surface for integrations that only need to store a secret, fetch it back, create a policy, and list roles. The fuller spec covers login and API-key authentication, Kubernetes mutual TLS, host factory tokens, public keys, resources, status, and certificate authority operations.
Which Conjur spec should an agent choose?
Use the compact spec when storing and retrieving secrets plus basic policy and role work is enough, because its small surface keeps calls simple. Use the fuller spec when a workflow needs Kubernetes workload authentication, host factory self-enrolment, or certificate authority operations that the compact spec does not expose.
Is CyberArk Conjur for human passwords or machine secrets?
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
