Install Jentic One Beta

Connect the Auxen Headless API to your agent

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

Deploy an open-weight model to a private endpoint and read its deployment id back

Switch the model on a running deployment or change its throughput

Run inference against a deployment through the Auxen-native or OpenAI-compatible chat endpoint

Pause and resume deployments to control spend

Read the account billing balance and set a per-deployment spending cap

GET STARTED

Start building with Auxen Headless API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Auxen Headless API for, with concrete tasks.

★ AI Agent Model Deployment

An AI agent spins up a private inference endpoint on demand without a developer clicking through a dashboard. Through Jentic the agent deploys an open-weight model, reads back the deployment id, and runs completions against it, while the account and deployment keys stay on the developer's own machine.

Deploy a model from the models list, capture the returned deployment id, and send a chat completion to confirm the endpoint responds

Deployment Cost Control

Private model endpoints cost money while they run, so teams pause them when idle and cap spend per deployment. Auxen lets an agent pause a deployment, resume it when traffic returns, read the account credit balance, and set a spending cap on a single deployment.

Pause an idle deployment, then set a spending cap on it before resuming so it cannot overspend the account balance

Live Model Switching

Teams iterate on which open-weight model serves a given endpoint. Auxen lets an agent switch the model on an existing deployment in place and adjust its throughput, so the endpoint URL stays stable while the model behind it changes.

Switch the model on a deployment to a newer open-weight model and raise its throughput for the expected load

Key Endpoints

42 endpoints — the auxen api deploys and manages private open-weight model endpoints and runs inference against them.

METHOD

PATH

DESCRIPTION

POST

/v1/deploy

Deploy a model

GET

/v1/deployments

List your deployments

GET

/v1/deployments/{deploymentId}

Get a deployment

POST

/v1/deployments/{deploymentId}/switch-model

Switch the model on a deployment

POST

/v1/deployments/{deploymentId}/pause

Pause a deployment

POST

/v1/{deploymentId}/chat

Run inference on a deployment

GET

/v1/models

List available models

GET

/v1/billing/balance

Get account billing snapshot

POST

/v1/deploy

Deploy a model

GET

/v1/deployments

List your deployments

GET

/v1/deployments/{deploymentId}

Get a deployment

POST

/v1/deployments/{deploymentId}/switch-model

Switch the model on a deployment

POST

/v1/deployments/{deploymentId}/pause

Pause a deployment

POST

/v1/{deploymentId}/chat

Run inference on a deployment

GET

/v1/models

List available models

GET

/v1/billing/balance

Get account billing snapshot

Why Jentic?

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

Setup

Wiring Auxen by hand means handling two token types, its account-level agent key and per-deployment inference keys, and polling deployment state yourself. Through Jentic you install once, import Auxen from the API Directory, store the key once, and your agent calls it.

Permission scoping

Auxen puts the deployment id in the URL path (/v1/deployments/{deploymentId}/...), so a rule can pin your agent to one deployment: it can run inference and read status for that deployment and nothing else. You choose which operations it may call, so destructive ones like deployment deletion are not included unless you add them.

Credential isolation

Your Auxen keys are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'deploy a model' or 'run a chat completion', and Jentic returns the matching Auxen operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Auxen Headless API through Jentic.

Is there an Auxen MCP server?

You don't need an MCP server to give your agent the Auxen API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. Operations are discovered on demand, so nothing extra is loaded into the agent's context.

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

Yes. Write a rule that allows only the inference and status-read operations under one deployment id, so the agent can run completions and check that deployment without deleting it or touching billing, and every call is logged.

What authentication does the Auxen Headless API use?

The Auxen API authenticates with bearer tokens: an account-level agent key authorizes deployment and billing operations, and a per-deployment inference key authorizes chat calls on a single deployment, per its OpenAPI spec. Through Jentic each token is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's prompt or logs.

Can I run a chat completion against a deployment with the Auxen API?

Yes. Each deployment exposes an Auxen-native chat endpoint and an OpenAI-compatible chat completions endpoint, both called with that deployment's inference key so you can hand the key to a downstream service without giving up management rights.

How do I deploy an Auxen model through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then import the Auxen API from the Jentic API Directory and store your agent key. Your agent searches for 'deploy an open-weight model' and Jentic returns the deploy operation with its input schema. To run it on your own infrastructure, install Jentic One from its GitHub repo.

What are the rate limits for the Auxen Headless API?

The Auxen OpenAPI spec does not define request rate limits. Auxen meters usage by USD-denominated credits and the per-deployment throughput you set, so check your plan's throughput tier and credit balance for the ceilings that apply.

Auxen Headless API

AI ReadinessFoundational (D-)43/100

See full scorecard

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

For Agents

Deploy open-weight models to private endpoints and run inference on them: deploy, switch models, change throughput, pause or resume, and read billing, with chat completions on each deployment.

Use for: Deploy an open-weight model to a private endpoint, I want to run a chat completion against one of my deployments, Switch the model running on a deployment, Pause a deployment to stop billing

Not supported: Does not handle model training, dataset labeling, or fine-tuning. Use for deploying open-weight models and running inference on them only.

The Auxen API deploys and manages private open-weight model endpoints and runs inference against them. It exposes operations to deploy a model, switch the model on a running deployment, change throughput, and pause or resume a deployment, each identified by a deployment id. Billing operations read the account balance, top up credits, and set per-deployment spending caps, while account-level agent keys and per-deployment inference keys keep management separate from calling.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C+Signals: 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).

50%

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

18%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

36%

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

24%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

55%

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

64%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Auxen Headless API to your agent

Capabilities

Start building with Auxen Headless API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Auxen Headless API

Jentic AI Readiness Score

Auxen Headless 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