Install Jentic One Beta

Connect the Consus Gateway API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Consus Gateway 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%2Fconsus.io%2Fconsus" | 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%2Fconsus.io%2Fconsus" | 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 Consus Gateway API.

Create chat completions through an OpenAI-compatible endpoint

Send native Anthropic Messages API requests

Generate embeddings for text

Count the tokens a Messages request will use

Issue, relabel, and revoke scoped inference keys

GET STARTED

Start building with Consus Gateway API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Consus Gateway API for, with concrete tasks.

★ Agent Inference Through a Gateway

An AI agent connected through Jentic can run its model calls through Consus instead of a provider directly: it creates a chat completion against a gateway model and reads the response. Because the surface is OpenAI-compatible, the agent uses the same request shape it would send to a standard chat endpoint while the gateway handles routing.

Create a chat completion against a gateway model and read the response

Anthropic-Compatible Messaging

Consus exposes the native Anthropic Messages API alongside a token-count endpoint, so a team can budget before it sends. An agent counts the tokens a Messages request will use, then creates the message, keeping request size and cost predictable on the gateway.

Count the tokens for a Messages request, then create the message

Embeddings for Retrieval

Semantic search needs vectors. Consus generates embeddings through the same gateway that serves chat, so an agent can embed a batch of documents for a retrieval index without wiring a second provider or credential.

Generate embeddings for a set of documents to index for semantic search

Key and Spend Governance

Running inference for an organization means controlling who spends what. Consus issues inference keys with a monthly spend limit, revokes them, and reports organization request logs and spend, so an agent can provision a bounded key and audit usage from one management surface.

Issue an inference key with a monthly spend limit and read the organization's recent request logs

Key Endpoints

16 endpoints — the consus gateway api routes ai inference to government-authorized cloud infrastructure behind openai- and anthropic-compatible surfaces.

METHOD

PATH

DESCRIPTION

POST

/v1/chat/completions

Create a chat completion

POST

/v1/messages

Create a native Anthropic Messages request

POST

/v1/embeddings

Create embeddings

POST

/v1/responses

Create an OpenAI-style response

GET

/v1/models

List available models

POST

/v1/keys

Create an inference key

POST

/v1/chat/completions

Create a chat completion

POST

/v1/messages

Create a native Anthropic Messages request

POST

/v1/embeddings

Create embeddings

POST

/v1/responses

Create an OpenAI-style response

GET

/v1/models

List available models

POST

/v1/keys

Create an inference key

Why Jentic?

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

Setup

Wiring Consus by hand means handling its x-api-key header, keeping the inference key separate from the management key, and matching OpenAI or Anthropic request shapes per endpoint. Through Jentic you install once, import Consus from the API Directory, store the key once, and your agent calls it.

Permission scoping

Consus separates inference from management with two key types, and the inference endpoints take their model and input in the request body rather than a resource in the URL path, so rules bound which operations your agent may call. Limit it to the inference operations it needs, such as chat completions and embeddings, and leave key and spend management out unless you add them.

Credential isolation

Your Consus 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 'create a chat completion' or 'generate embeddings', and Jentic returns the matching Consus operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Consus Gateway API through Jentic.

What authentication does the Consus Gateway API use?

The Consus Gateway API authenticates with an API key in the x-api-key header. Inference endpoints use a standard inference key, while the key and organization management operations use a separate management key, both per its OpenAPI spec. When you call it through Jentic, the key is stored once by your own Jentic One instance and injected at execution time, so it never reaches the agent's prompt or logs.

Is the Consus Gateway compatible with OpenAI and Anthropic clients?

Yes. The gateway exposes OpenAI-compatible chat completions and responses and the native Anthropic Messages API, so you can point an existing OpenAI or Anthropic client at it by changing only the base URL and API key.

Does the Consus Gateway run on government-authorized infrastructure?

Per its documentation the gateway routes inference to government-authorized cloud environments, such as FedRAMP and DoD impact levels, behind the compatible surfaces. This lets regulated workloads use standard inference request shapes while the gateway handles where the compute runs.

What are the rate limits for the Consus Gateway API?

The spec notes that each key carries a per-second rate limit, a burst allowance, and a monthly quota enforced at the gateway, but does not state the numeric values. See the Consus gateway documentation at https://gateway.consus.io for the limits attached to your key.

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

Yes. Consus separates inference from management, and the inference endpoints take their model and input in the request body, so rules bound which operations the agent may call. Write a rule that allows only the chat-completion and embeddings operations, so the agent can run inference but cannot issue or revoke keys or change spend limits, and every call it makes is logged.

How do I create a chat completion with the Consus Gateway API through Jentic?

Search Jentic with an intent like 'create a chat completion', and Jentic returns the chat completions operation at /v1/chat/completions with its input schema so your agent passes the model and messages. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Consus MCP server?

You don't need an MCP server to give your agent the Consus Gateway. Jentic connects it directly from the API Directory: import the API, store your key once, and your agent calls the inference and management operations on demand.

Consus Gateway API

AI ReadinessFoundational (C+)59/100

See full scorecard

Official vendor OpenAPI document · agent-readyAI/MLLanguage ModelsapiKey16 EndpointsREST

For Agents

Run chat completions, Anthropic messages, OpenAI responses, and embeddings through an OpenAI- and Anthropic-compatible inference gateway, and manage scoped keys and spend with Consus.

Use for: Create a chat completion, Send a message to an Anthropic-compatible model, Generate embeddings for a batch of text, Count the tokens in a request before sending it

Not supported: Does not train or fine-tune models, and does not host a vector database. Use for routed AI inference, embeddings, and inference-key governance only.

The Consus Gateway API routes AI inference to government-authorized cloud infrastructure behind OpenAI- and Anthropic-compatible surfaces. It creates chat completions, native Anthropic messages, OpenAI-style responses, and embeddings, counts tokens for a request, and lists the available models. A management surface issues and revokes inference keys, sets per-key monthly spend limits, and reads organization request logs and spend. Authentication uses an API key in the x-api-key header, with a separate management key for the key and organization operations.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: DSignals: 4

86%

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

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.

66%

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

36%

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.

52%

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: C-Signals: 1

50%

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: A-Signals: 1

77%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Consus Gateway API to your agent

Capabilities

Start building with Consus Gateway API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Consus Gateway API

Jentic AI Readiness Score

Consus Gateway 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