Install Jentic One Beta

Connect the Orquesta Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Orquesta Public 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%2Fgetorquesta.com%2Fgetorquesta" | 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%2Fgetorquesta.com%2Fgetorquesta" | 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 Orquesta Public API.

Route chat completions across upstream models through the OpenAI-compatible Batuta proxy

List the models available through the Batuta proxy

Submit a prompt for execution and cancel a pending or running one

List and read prompts in your organization with their context

List execution logs filtered by prompt or project

GET STARTED

Start building with Orquesta Public API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Orquesta Public API for, with concrete tasks.

★ Model-Routed Chat Completions

An AI agent connected through Jentic sends an OpenAI-compatible chat-completions request to Orquesta's Batuta proxy, which classifies the prompt and routes it to a suitable upstream model, so the agent gets a completion without picking or wiring a model itself. Calling one endpoint keeps the agent's integration stable while Orquesta decides where the request goes.

Send a chat-completions request to the Batuta proxy and return the routed model's completion

Prompt Execution and Cancellation

A workflow submits a prompt for execution and cancels it if it is still pending or running, using the prompt operations to control long-running work. Reading the prompt back with its context lets the agent confirm what was run before acting on the result.

Submit this prompt for execution, then cancel it if it has not completed within the time limit

Execution Log Review

A monitoring workflow lists execution logs by prompt or project to review what ran and how, pulling the record Orquesta keeps for each execution. This gives an agent or an operator a read-only trail without opening the dashboard.

List the execution logs for this project and summarise the most recent runs

Key Endpoints

11 endpoints — the orquesta public api centres on batuta, an openai-compatible chat-completions proxy that routes a request across multiple upstream models using per-prompt classification, so an application calls one endpoint and orquesta picks the model.

METHOD

PATH

DESCRIPTION

POST

/api/v1/chat/completions

Create a chat completion (OpenAI-compatible)

GET

/api/v1/models

List models available through Batuta

POST

/api/v1/prompts

Submit a prompt for execution

GET

/api/v1/prompts

List prompts in your organization

POST

/api/v1/prompts/{id}/cancel

Cancel a pending or running prompt

GET

/api/v1/logs

List execution logs by prompt or project

GET

/api/v1/projects

List projects in your organization

GET

/api/v1/agents

List registered agents and their status

POST

/api/v1/chat/completions

Create a chat completion (OpenAI-compatible)

GET

/api/v1/models

List models available through Batuta

POST

/api/v1/prompts

Submit a prompt for execution

GET

/api/v1/prompts

List prompts in your organization

POST

/api/v1/prompts/{id}/cancel

Cancel a pending or running prompt

GET

/api/v1/logs

List execution logs by prompt or project

GET

/api/v1/projects

List projects in your organization

GET

/api/v1/agents

List registered agents and their status

Why Jentic?

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

Setup

Wiring the Orquesta API by hand means choosing between its bearer token and X-API-Key credentials, carrying one on each request, and integrating the OpenAI-compatible proxy alongside the prompt and log endpoints yourself. Through Jentic you install once, import Orquesta from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Most of the Orquesta surface is read-only, so a rule can allow your agent to list prompts, logs, models, and projects while leaving the write operations out. You choose which operations it may call, so submitting or cancelling a prompt is not included unless you add it.

Credential isolation

Your Orquesta bearer token or API 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 'route a chat completion' or 'list execution logs', and Jentic returns the matching Orquesta operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Orquesta Public API through Jentic.

Is there an Orquesta MCP server?

You don't need an MCP server to give your agent the Orquesta API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent can route chat completions and read prompts straight away, with no extra server to run and no tool definitions to load into the agent's context.

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

Yes. Write a rule that allows only the read operations the agent needs, such as listing prompts, logs, and models, so it can review activity without submitting or cancelling prompts. Write operations like submitting or cancelling a prompt are not included unless you add them, and every call the agent makes is logged.

What authentication does the Orquesta API use?

The Orquesta API accepts two credentials per its OpenAPI spec: a bearer token in the Authorization header, or an API key in the `X-API-Key` header. Through Jentic the credential is stored encrypted by your own instance and injected at call time, so it never appears in the agent's prompt or logs.

How does the Batuta proxy choose a model?

The chat-completions endpoint is OpenAI-compatible and routes each request across multiple upstream models using per-prompt classification, so your agent calls one endpoint and Orquesta selects the model. You can list the models available through the proxy to see what it can route to.

What are the rate limits for the Orquesta API?

The OpenAPI spec does not specify rate limits for the Orquesta API. For current limits and token formats, see the Orquesta documentation at https://getorquesta.com.

How do I route a chat completion through Jentic?

Import the Orquesta API from the Jentic API Directory, then have your agent issue a request such as 'route this chat completion across models'. Jentic matches the intent to the chat-completions operation and returns its input schema so the agent sends the request correctly, with your stored credential injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Getorquesta Orquesta Public API

AI ReadinessAI-Aware (B-)61/100

See full scorecard

Official vendor OpenAPI document · agent-readyAI/MLLanguage Modelsbearer, apiKey11 EndpointsREST

For Agents

Route OpenAI-compatible chat completions across models through Orquesta's Batuta proxy, submit and cancel prompts, and read execution logs. Authenticates with a bearer token or an API key.

Use for: Create a chat completion routed across models, List the models available through Batuta, Submit a prompt for execution, Cancel a running prompt

Not supported: Does not train or host the underlying models, store vector embeddings, or manage billing. Use for routing chat completions, prompt execution, and reading execution logs in Orquesta only.

The Orquesta Public API centres on Batuta, an OpenAI-compatible chat-completions proxy that routes a request across multiple upstream models using per-prompt classification, so an application calls one endpoint and Orquesta picks the model. Alongside the proxy it exposes the organization's prompts, which can be listed, read with their context, submitted for execution, updated, and cancelled, plus the execution logs those runs produce. It also gives read access to projects, registered agents and their online status, and the users in scope.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: CSignals: 4

81%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

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

35%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

59%

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

29%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

62%

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

55%

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

83%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Orquesta Public API to your agent

Capabilities

Start building with Orquesta Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Getorquesta Orquesta Public API

Jentic AI Readiness Score

Orquesta Public 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