The 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 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.
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.
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" | 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%2Fjentic.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.
BOOK A DEMO
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.