jentic/jentic-one

Connect an agent to any API you need, and enforce exactly what it is allowed to call.
Quickstart ·
First brokered call ·
API Directory ·
Security ·
Discussions
> [!NOTE]
> Public Beta. Schemas and CLI commands can change between 0.x releases. Pin a version if
> you need stability. Contributions are welcome: see CONTRIBUTING.md and the
> open issues.
## What Jentic One is
Giving an agent API access normally means giving it an API key. Jentic One removes that step.
Register the APIs an agent may use, store the credentials once, and the agent makes its calls through the Broker. The Broker checks the agent's permissions, attaches the credential at execution time, and writes an execution record. Your agent never sees your keys.
Agents integrate through the jentic CLI, a generated skill, the local jentic mcp server,
or plain HTTP. Every path terminates at the credential-injecting Broker: the MCP server runs beside the
agent as a thin client and holds no upstream credentials — those never leave your Broker.
Who it's for: developers running a coding agent locally (Claude Code,
Codex, Cursor, Cline, or one you built) that needs real API access; small
teams running agents in a private network or VPC; anyone who needs to pass a
security review before an agent touches production credentials.
## Quickstart
The open-source build is the real thing, not a trial — the same code,
broker, and security model as every other install shape. Every path below
runs on Linux and macOS; on Windows, follow the
Windows guide (WSL2 + native jentic.exe).
### Self-hosted (Docker)
One image (ghcr.io/jentic/jentic-one-app) runs both the control plane and the
broker. The quickstart shape below keeps everything in SQLite files on one
volume and runs with development-mode secrets — don't point it at a real
credential (the quickstart config also ships no encryption keyset, so storing
one fails until you configure credentials.encryption):
bash
docker pull ghcr.io/jentic/jentic-one-app:latest
docker volume create jentic-data
# Grab the quickstart config (SQLite on the volume; fetched from main) — tweak it, or use as is
curl -fsSLO https://raw.githubusercontent.com/jentic/jentic-one/main/config/quickstart.env
# Migrate, then start the two roles
docker run --rm --env-file quickstart.env -v jentic-data:/data \
ghcr.io/jentic/jentic-one-app:latest python -m jenticone.migrations.run
docker run -d --name jentic-app --env-file quickstart.env -v jentic-data:/data \
-p 127.0.0.1:8000:8000 ghcr.io/jentic/jentic-one-app:latest # control plane (UI + APIs)
docker run -d --name jentic-broker --env-file quickstart.env -e JENTICAPPS=broker -v jentic-data:/data \
-p 127.0.0.1:8100:8000 ghcr.io/jentic/jentic-one-app:latest # data plane (agents call this)
# First admin (prompts for a password), then sign in at http://127.0.0.1:8000
docker run --rm -it --env-file quickstart.env -v jentic-data:/data \
ghcr.io/jentic/jentic-one-app:latest python -m jenticone create-admin --email you@example.com
curl -fsS http://127.0.0.1:8000/health # verify the control plane is up
Prefer one file? The
quickstart compose file has
the same settings built in and runs the migrations, the control plane and the