Install Jentic One Beta

Connect the Jentic One Broker API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Jentic One Broker 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-broker" | 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-broker" | 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 One Broker API.

Forward read requests to an upstream API with the caller's credentials injected at the proxy

Forward write requests to an upstream API without exposing the secret to agent code

Return the upstream response synchronously, or a 202 polling link for long-running calls

Route all outbound API traffic through one auditable egress point

GET STARTED

Start building with Jentic One Broker API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Jentic One Broker API for, with concrete tasks.

★ Agent calls third-party APIs without touching secrets

An AI agent needs to call several third-party APIs but should never see their credentials. The Jentic One Broker API injects each upstream credential at the proxy, so the agent sends only the upstream URL and payload while the secret stays on the server. Through Jentic the agent discovers the forwarding operation by intent and the credential is supplied at call time.

Forward a POST payload to an upstream API through the broker and read back the upstream response without ever holding the upstream credential

Single auditable egress point

A team wants every outbound API call from its agents to pass through one place that can be logged and controlled. The Jentic One Broker API gives outbound traffic a single choke-point: it forwards method, headers, and body unchanged, so existing upstream integrations keep working while every call is observable from one spot.

Route an upstream GET through the broker so the call is captured at the central egress point and the response is returned unchanged

Long-running upstream calls

Some upstream operations take longer than a synchronous request can wait. The Jentic One Broker API returns the upstream body with a 200 for fast calls and falls back to a 202 with a polling link for slow ones, so an agent can start the work and poll for the result instead of holding a connection open.

Forward a slow upstream request, receive the 202 polling link, and poll until the upstream result is ready

Key Endpoints

9 endpoints — the jentic one broker api is a stateless data-plane proxy that forwards any http request to an upstream api with the caller's stored credentials injected at the edge.

METHOD

PATH

DESCRIPTION

GET

/{upstream_url}

Execute a GET against an upstream API

POST

/{upstream_url}

Execute a POST against an upstream API

PUT

/{upstream_url}

Execute a PUT against an upstream API

DELETE

/{upstream_url}

Execute a DELETE against an upstream API

GET

/health

Service health probe

GET

/ready

Saturation-aware readiness probe

GET

/{upstream_url}

Execute a GET against an upstream API

POST

/{upstream_url}

Execute a POST against an upstream API

PUT

/{upstream_url}

Execute a PUT against an upstream API

DELETE

/{upstream_url}

Execute a DELETE against an upstream API

GET

/health

Service health probe

GET

/ready

Saturation-aware readiness probe

Why Jentic?

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

Setup

Wiring secure outbound calls by hand means building a proxy, holding upstream secrets in agent-reachable config, and handling retries and long-call polling yourself. Through Jentic you install once, import the Jentic One Broker from the API Directory, store the bearer token once, and your agent proxies upstream calls through it.

Permission scoping

The Jentic One Broker splits forwarding by HTTP method, so you choose which methods the agent may proxy: a rule can allow read forwarding and withhold delete forwarding. You decide the operation set, so destructive forwards are not included unless you add them.

Credential isolation

Your Jentic One Broker 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 'call an upstream API with injected credentials', and Jentic returns the matching Jentic One Broker operation with its input schema so the agent forwards the right request without reading the reference docs.

FAQs

Specific to using Jentic One Broker API through Jentic.

What authentication does the Jentic One Broker API use?

The Jentic One Broker API authenticates the caller with a bearer token, per its OpenAPI spec. The upstream credentials it injects into forwarded requests are held separately and never travel back to the agent. 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 forward long-running calls through the Jentic One Broker API?

Yes. The Jentic One Broker returns the upstream body with a 200 for fast calls and falls back to a 202 with a polling link for long-running ones, so your agent can start the work and poll for the result rather than hold a connection open. The method, headers, and body are forwarded unchanged in both cases.

Can I limit what my agent is allowed to do with the Jentic One Broker API?

Yes. The forwarding operations are split by HTTP method, so a rule can allow read forwarding while withholding the delete-forwarding operation, letting the agent proxy safe calls and nothing destructive unless you add it. Every forwarded call passes the single egress point and is logged.

Is there a Jentic One Broker API MCP server?

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

How do I proxy an upstream API call through Jentic?

Search Jentic for an intent such as 'call an upstream API with injected credentials' and it returns the matching forwarding operation with its input schema, so your agent sends the upstream URL and payload while the secret stays on the server. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Jentic One Broker API

Browse all Jentic APIs

AI ReadinessAI-Ready (A)85/100

See full scorecard

Official vendor OpenAPI document · agent-readySecuritySecrets Managementbearer9 EndpointsREST

For Agents

Proxy authenticated HTTP calls to any upstream API through a stateless broker that injects stored credentials at the edge, so agent code never holds the secret. Returns the upstream response or a polling link for long calls.

Use for: Call an upstream API without handling its credentials, Forward a request to a third-party API through the broker, Proxy a write to an upstream service securely, Check whether the broker is ready to accept traffic

Not supported: Does not store credentials, define permission rules, or register upstream APIs. Use for forwarding authenticated requests to upstream APIs only.

The Jentic One Broker API is a stateless data-plane proxy that forwards any HTTP request to an upstream API with the caller's stored credentials injected at the edge. The caller sends the upstream URL as the request path, and the Jentic One Broker forwards the method, headers, and body unchanged, returns the upstream response synchronously, or falls back to a 202 with a polling link for long-running calls. Because secrets are injected at the proxy, they stay off the agent and the end-user device, outbound traffic has one auditable egress point, and upstream credentials rotate centrally without redeploying callers.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

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).

100%

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: ASignals: 4

44%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

97%

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: ASignals: 4

86%

Description Coverage

Coverage of descriptions across API elements.

89%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

83%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

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: ASignals: 1

82%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Jentic One Broker API to your agent

Capabilities

Start building with Jentic One Broker API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Jentic One Broker API

Jentic AI Readiness Score

Broker 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