Install Jentic One Beta

Connect the Jentic Control Plane API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Jentic Control Plane 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%2Fjentic.com%2Fjentic-one-control" | sh

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%2Fjentic.com%2Fjentic-one-control" | 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 Jentic Control Plane API.

Store, rotate, and delete upstream API credentials

Write permission rule sets that bound which operations an agent may call

Import and manage the API specs the platform is allowed to call

Search registered operations by intent and inspect their input schema

GET STARTED

Start building with Jentic Control Plane API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Jentic Control Plane API for, with concrete tasks.

★ Provision a scoped agent

Before an agent can call anything, an operator registers it, stores the upstream credential, and binds the two with a permission rule set that names the allowed operations. The Jentic Control Plane API performs each of these steps, so the agent starts life with exactly the access it needs. Through Jentic the operations are discovered by intent and executed against your own instance.

Register an agent, store an upstream credential, and attach a permission rule set that allows only the read operations the agent needs

Governed API catalog

An operator curates which third-party APIs the platform may call by importing their specs and reviewing the operations each one exposes. The Jentic Control Plane API imports specs, lists registered APIs, and lets an agent search operations by intent before any call is made, so the surface an agent can reach is deliberate rather than open-ended.

Import an OpenAPI spec, list the operations it exposes, and search for the one that matches a given intent

Audit and usage review

A team needs to see what its agents actually did. The Jentic Control Plane API lists executions, events, and usage statistics and exposes an audit log, so an operator can trace which operation an agent ran, when, and under which credential binding. This turns agent activity into a reviewable record rather than an opaque stream of outbound calls.

List recent executions and open the audit entry for one of them to see which operation ran and under which credential

Key Endpoints

169 endpoints — the jentic control plane api administers which registered apis an agent may call, for whom, with which credentials, and with what telemetry retained.

METHOD

PATH

DESCRIPTION

GET

/agents

List registered agents

POST

/agents

POST

/credentials

Store an upstream credential

POST

/permission-rule-sets

Create a permission rule set

POST

/search

Search registered operations by intent

GET

/audit

List audit entries

GET

/agents

List registered agents

POST

/agents

POST

/credentials

Store an upstream credential

POST

/permission-rule-sets

Create a permission rule set

POST

/search

Search registered operations by intent

GET

/audit

List audit entries

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Governing agent access by hand means building credential storage, a rules engine, agent registration, and an audit trail yourself. Through Jentic you install once, import the control plane from the API Directory, store the bearer token once, and your agent calls the administration operations it needs.

Permission scoping

The control plane carries agent and credential ids in the URL path, so a rule can pin your agent to one record and the operations you pick: it can read the audit log and list agents without gaining the create or delete operations unless you add them.

Credential isolation

Your control-plane bearer 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 'write a permission rule set' or 'store a credential', and Jentic returns the matching control-plane operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Jentic Control Plane API through Jentic.

What authentication does the Jentic Control Plane API use?

The Jentic Control Plane API authenticates with a bearer token, per its OpenAPI spec. The upstream credentials it manages are stored separately and are never returned to callers in plaintext. Through Jentic the bearer token is stored once and injected at call time, so it never enters the agent's prompt, logs, or context.

Can I write permission rules with the Jentic Control Plane API?

Yes. The permission-rule-set operations let you create a rule set that names which operations an agent may call and attach it to a credential binding, and a dry-run operation evaluates a rule set before you commit it. The agent then runs only the operations the attached rules allow.

Can I limit what my agent is allowed to do with the Jentic Control Plane API?

Yes. The control plane carries agent and credential ids in the URL path, such as the agent and credential record operations, so a rule can pin your agent to the specific records and the operations you pick, for example reading the audit log without creating or deleting agents. Every call it makes is logged.

Is there a Jentic Control Plane API MCP server?

You don't need an MCP server to give your agent the Jentic Control Plane API. Jentic connects it directly from the API Directory: import it, store your bearer token once, and your agent calls it. Operations are discovered on demand, so no extra tool definitions sit in the agent's context.

How do I provision a scoped agent through Jentic?

Search Jentic for an intent such as 'register an agent and bind a credential' and it returns the matching operations with their input schemas, so your agent registers the record, stores the credential, and attaches a rule set in sequence. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Jentic Control Plane API

Browse all Jentic APIs

AI ReadinessAI-Aware (B+)69/100

See full scorecard

Official vendor OpenAPI document · agent-readyIdentity AuthAuthorizationbearer169 EndpointsREST

For Agents

Administer credentials, permission rule sets, registered APIs, and agent identities, and review an audit log of executions and events. The control layer that governs what an agent is allowed to call.

Use for: Store a new upstream credential, Write a permission rule set for an agent, Register an agent and bind a credential to it, List all registered APIs on the instance

Not supported: Does not forward upstream API requests, run agent workloads, or host end-user data. Use for administering credentials, permission rules, agents, and audit on your own instance only.

The Jentic Control Plane API administers which registered APIs an agent may call, for whom, with which credentials, and with what telemetry retained. It stores and rotates credentials, writes permission rule sets, registers and scopes agents, imports and manages API specs, and keeps an audit log of executions and events. It is the administrative counterpart to the data-plane proxy: where the proxy executes upstream calls, the control plane decides what those calls are allowed to be.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

95%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

21%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

20%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

74%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: A-Signals: 4

56%

Description Coverage

Coverage of descriptions across API elements.

91%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

98%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

56%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: C+Signals: 1

58%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B+Signals: 1

68%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Jentic Control Plane API to your agent

Capabilities

Start building with Jentic Control Plane API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Jentic Control Plane API

Jentic AI Readiness Score

Jentic Control Plane API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness