Install Jentic One Beta

Connect the openbash to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the openbash, 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%2Fopenbash.ai%2Fopenbash" | 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%2Fopenbash.ai%2Fopenbash" | 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 openbash API.

Run one shell command or a piped pipeline of programs and read its output, exit_code, and duration_ms

Stream command output as Server-Sent Events by setting stream to true

Open or resume a session that keeps the working directory, environment, and /tmp across calls

Read a file back from a session's /tmp scratch space, or from the bundle a submission froze

GET STARTED

Start building with openbash API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use openbash API for, with concrete tasks.

★ AI agent running data programs as shell pipelines

An AI agent working through Jentic searches for 'run a shell command on openbash', loads the exec operation, and sends one command line that pipes several programs together. The response returns the program output with an exit_code where 0 means results, 2 means not entitled, and 3 means no results found, so the agent can tell an empty answer from a missing entitlement. Your own Jentic One instance injects the bearer key at call time.

Call GET /api/v1/programs/{slug} to read a program's help, then POST /api/v1/exec with a command that pipes that program into jq and sort, and report output and exit_code

Stateful multi-step research in a session

Some work needs files and environment to persist between steps. POST /api/v1/sessions returns a session_id, and commands sent to POST /api/v1/sessions/{id}/exec share that shell's working directory, environment, and /tmp. Drafts written in /tmp can be fetched with GET /api/v1/sessions/{id}/tmp/{path}, and DELETE /api/v1/sessions/{id} ends the shell when the work is finished.

Open a session with POST /api/v1/sessions, run two commands in it with POST /api/v1/sessions/{id}/exec that write and then transform a file in /tmp, read the result with GET /api/v1/sessions/{id}/tmp/{path}, then close it

Program discovery before execution

The program index is public, so an agent can learn what exists before it holds a key. GET /api/v1/programs lists programs with slug, domain, tier (free, metered, or contract), and status, and accepts a domain filter. With a key, each entry shows whether your account has it enabled, and GET /api/v1/key returns the account and its programs_enabled list.

Call GET /api/v1/programs with domain=housing, then GET /api/v1/key, and return the programs in that domain that are enabled for this account

Key Endpoints

13 endpoints — the openbash api runs shell commands against a hosted set of data programs through a single execution endpoint.

METHOD

PATH

DESCRIPTION

POST

/api/v1/exec

Run one shell command or pipeline

POST

/api/v1/sessions

Open or resume a session

POST

/api/v1/sessions/{id}/exec

Run a command inside a session

GET

/api/v1/sessions/{id}/tmp/{path}

Read a file from session scratch

GET

/api/v1/programs

List programs in the catalog

GET

/api/v1/programs/{slug}

Get one program with help text

GET

/api/v1/key

Show the key's account and enabled programs

POST

/api/v1/exec

Run one shell command or pipeline

POST

/api/v1/sessions

Open or resume a session

POST

/api/v1/sessions/{id}/exec

Run a command inside a session

GET

/api/v1/sessions/{id}/tmp/{path}

Read a file from session scratch

GET

/api/v1/programs

List programs in the catalog

GET

/api/v1/programs/{slug}

Get one program with help text

GET

/api/v1/key

Show the key's account and enabled programs

Why Jentic?

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

Setup

Wiring openbash by hand means getting a key through the emailed-code exchange, sending it as a bearer token, tracking session ids across calls, and handling streamed output and the 1 MiB non-streaming cap. Through Jentic you install once, import openbash from the API Directory, store the key once, and your agent calls it.

Permission scoping

Rules bound openbash by operation: the command line travels in the POST /api/v1/exec body, so a rule decides whether your agent may execute at all, not which program it runs. You choose the operations it may call, so execution and DELETE /api/v1/sessions/{id} are not included unless you add them, leaving program index reads on their own.

Credential isolation

Your openbash key 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 'run a shell command' or 'list available programs', and Jentic returns the matching openbash operation with its input schema, including command, stream, and session_id, so the agent calls it directly.

FAQs

Specific to using openbash API through Jentic.

What authentication does the openbash API use?

The openbash API uses a bearer token per its OpenAPI spec: send your key as Authorization: Bearer. Execution, session, run, and key endpoints require it. The program index reads (programs, a program's help, program surface reads, and the changelog) accept calls with or without a key, and POST /api/auth/ssh is public: call it with an email to receive a code, then again with the code as otp to receive a key. Through Jentic the key is stored by your own instance and attached at call time.

Can I keep state between commands with the openbash API?

Yes. Calls to POST /api/v1/exec are stateless by default. Open a session with POST /api/v1/sessions, or pass resume with an earlier id, and run commands with POST /api/v1/sessions/{id}/exec to keep the working directory, environment, and /tmp. End it with DELETE /api/v1/sessions/{id}; simply stopping is a detach, and the session stays resumable under its id.

What are the rate limits for the openbash API?

The OpenAPI spec does not state a numeric limit; it documents a 429 response when an account is rate limited, and a 504 when a command does not finish in time. Non-streaming output is capped at 1 MiB, flagged by the truncated field, so stream large output instead. See https://openbash.ai for current account limits.

Is there an openbash MCP server?

You don't need an MCP server to give your agent openbash. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the execution, session, and program index operations on demand without loading another server's tool definitions into its context.

How do I run an openbash pipeline through Jentic?

Search Jentic for 'run a shell command on openbash', load the POST /api/v1/exec operation, and execute it with a command string such as a program piped into jq. Check exit_code in the response: a non-zero exit is a result, not an HTTP failure. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the openbash API?

Yes, at the operation level. For a read-only program index assistant, write a rule that allows GET /api/v1/programs and GET /api/v1/programs/{slug} only, and the agent can browse programs and their help but cannot execute anything or close sessions. If you allow POST /api/v1/exec, the command line travels in the request body, so the rule decides whether the agent may run commands, not which commands; which programs exist is set by your account's enablement.

openbash

AI ReadinessAI-Aware (B-)62/100

See full scorecard

Official vendor OpenAPI document · agent-readyCloud InfrastructureServerlessbearer13 EndpointsREST

For Agents

Run shell commands and pipelines over openbash's hosted data programs, keep state in resumable sessions, and browse the program index with each program's help text.

Use for: Run this pipeline of openbash programs and give me the output, List all programs available in the housing domain, Get the help text for an openbash program before I call it, I want to keep a working directory between commands

Not supported: Does not host your own code, deploy containers, or provision virtual machines. Use for running openbash's hosted data programs as shell commands only.

The openbash API runs shell commands against a hosted set of data programs through a single execution endpoint. Programs are commands rather than routes, so a pipeline of several of them piped through tools like jq and sort is one POST /api/v1/exec request, and the response carries the interleaved output, an exit_code, and a duration. Calls are stateless by default; opening a session keeps a working directory, environment, and /tmp across calls, and files in that scratch space can be read back over HTTP. The public program index endpoints list every program with its domain, tier, and help text, and mark which ones your account has enabled.

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

98%

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: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

44%

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: D-Signals: 4

33%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

85%

OperationId Quality

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

48%

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

63%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the openbash to your agent

Capabilities

Start building with openbash API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

openbash

Jentic AI Readiness Score

openbash

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