Install Jentic One Beta

Connect the Hydracept Public API to your agent

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

Search the capability list by task query and describe a capability with its execution targets and benchmarks

Quote a capability charge before running it, then invoke it or submit it as a durable job

Follow a job through its events, approve, reject, or cancel it, and fetch its result, receipt, and artifacts

GET STARTED

Start building with Hydracept Public API

Explore with Jentic One

View OpenAPI Document

Use Cases

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

★ Agent-run AI jobs with receipts through Jentic

A developer's agent calls AI capabilities through Hydracept and keeps a receipt for each one. Through Jentic the agent finds the quote, job, and receipt operations by intent; the Hydracept API key is injected by the developer's own Jentic One instance, and a rule can confine the agent to one capability key so it cannot touch connections, keys, or the wallet.

Call POST /v1/capabilities/{capability_key}/quote with capability_key image.generate.v1 and the prompt input, submit POST /v1/capabilities/image.generate.v1/jobs with the same input, poll GET /v1/jobs/{job_id} until it finishes, then fetch GET /v1/jobs/{job_id}/receipt

Brand-consistent image generation with LoRA adapters

Keep generated images on brand by registering a LoRA adapter for the project and referring to it through a stable alias. Uploads take the weights file and a displayName, aliases have immutable versions and explicit promotions, and a project default can map a capability to an alias, so jobs keep using the approved adapter until someone promotes a new one.

Call POST /v1/adapters/upload with the weights file and displayName 'Brand style v3', create an alias with POST /v1/adapter-aliases targeting the new adapter, then set it as the image.generate.v1 project default with PUT /v1/adapter-defaults/{capability_key}

Provider comparison before switching

Decide between providers on evidence rather than guesswork. The comparison call runs the same capability input against several competitors, the estimate call prices that comparison first, and the competitor-options call lists the default providers to compare for a capability.

Call GET /v1/capabilities/{capability_key}/comparisons/competitor-options, price two of them with POST /v1/capabilities/{capability_key}/comparisons/estimate, then run POST /v1/capabilities/{capability_key}/comparisons with context and those competitors

Reliable job notifications

Get notified when jobs finish instead of polling. A delivery endpoint takes a url and a signing secret, can be limited to chosen eventTypes, and every delivery attempt is listed with its state, filterable by endpoint or job, so a failed delivery can be found and replayed.

Call GET /v1/deliveries with jobId job_8f2 to find its failed delivery, then call POST /v1/deliveries/{delivery_id}/replay for it

Key Endpoints

131 endpoints — the hydracept public api runs external ai capabilities, such as image.

METHOD

PATH

DESCRIPTION

GET

/v1/capabilities

List capabilities

POST

/v1/capabilities/{capability_key}/quote

Quote a capability charge

POST

/v1/capabilities/{capability_key}/invoke

Invoke a capability

POST

/v1/capabilities/{capability_key}/jobs

Submit a capability job

GET

/v1/jobs/{job_id}/result

Get a job result

GET

/v1/jobs/{job_id}/receipt

Get a job receipt

POST

/v1/adapters/upload

Upload and register LoRA weights

POST

/v1/deliveries/{delivery_id}/replay

Replay a delivery

GET

/v1/capabilities

List capabilities

POST

/v1/capabilities/{capability_key}/quote

Quote a capability charge

POST

/v1/capabilities/{capability_key}/invoke

Invoke a capability

POST

/v1/capabilities/{capability_key}/jobs

Submit a capability job

GET

/v1/jobs/{job_id}/result

Get a job result

GET

/v1/jobs/{job_id}/receipt

Get a job receipt

POST

/v1/adapters/upload

Upload and register LoRA weights

POST

/v1/deliveries/{delivery_id}/replay

Replay a delivery

Why Jentic?

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

Setup

Wiring the Hydracept Public API by hand means sending its bearer key, threading quote ids into job submissions, polling or streaming job events, and keeping track of projects, environments, and provider bindings. Through Jentic you install once, import Hydracept from the API Directory, store the key once, and your agent calls it.

Permission scoping

Hydracept puts the capability key and job id in the URL path (/v1/capabilities/{capability_key}/..., /v1/jobs/{job_id}/...), so a rule can pin your agent to one capability such as image.generate.v1. You choose the operations it may call, so destructive ones like deleting API keys or revoking provider credentials are not included unless you add them.

Credential isolation

Your Hydracept 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 'generate an image' or 'get a job receipt', and Jentic returns the matching Hydracept operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Hydracept Public API through Jentic.

What authentication does the Hydracept Public API use?

Per its OpenAPI spec, the Hydracept Public API uses a Hydracept API key sent as a bearer token in the Authorization header. A handful of discovery operations, such as listing and describing capabilities, resolving a capability, and the agent-context call, need no credential. Through Jentic the key is stored encrypted by your own Jentic One instance and injected per call.

Can I see the cost of a Hydracept job before running it?

Yes. POST /v1/capabilities/{capability_key}/quote and the matching estimate call return a charge quote for a given input, and the execution options on a job accept a quoteId and a maximumCharge. After a run, GET /v1/jobs/{job_id}/receipt returns the job's receipt and the wallet settlement call shows what was charged.

Does Hydracept support bring-your-own-key provider credentials?

Yes. You can create connections to upstream providers with POST /v1/connections, store organization-level provider credentials, rotate them, and bind them to a project and environment. Those provider secrets live in Hydracept; through Jentic, your agent only uses the Hydracept API key.

What are the rate limits for the Hydracept Public API?

The OpenAPI spec does not specify rate limits. Check Hydracept's documentation at https://api.hydracept.com for current limits.

How do I run an image generation job with the Hydracept API through Jentic?

Search Jentic for 'submit an image generation job' to get POST /v1/capabilities/image.generate.v1/jobs, send the input, then poll GET /v1/jobs/{job_id} and fetch the output with GET /v1/jobs/{job_id}/result. To run it on your own infrastructure, install Jentic One from its GitHub repo and store your Hydracept key once.

Is there a Hydracept MCP server?

You don't need an MCP server to give your agent Hydracept. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent finds the operations it needs on demand, without a large set of tool definitions sitting in its context.

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

Yes. For example, write a rule that allows only the quote and jobs operations under /v1/capabilities/image.generate.v1 plus GET /v1/jobs/{job_id}/result, so the agent can price and run image jobs and read their output but cannot create API keys, rotate provider credentials, or open a wallet top-up session. Your Jentic One instance logs the calls it makes.

Hydracept Public API

AI ReadinessAI-Aware (B-)61/100

See full scorecard

Official vendor OpenAPI document · agent-readyAI/MLMl Inferencebearer131 EndpointsREST

For Agents

Discover and quote Hydracept AI capabilities, run them as invocations or durable jobs, read job results, receipts, and artifacts, and manage the LoRA adapters, provider connections, and webhook deliveries behind them.

Use for: Find a Hydracept capability that can generate product images, Quote what an image.generate.v1 job will cost before I run it, Submit an image generation job and wait for the result, Get the receipt for job job_8f2

Not supported: Does not train foundation models, host your own application, or replace the upstream provider accounts it connects to. Use for running and auditing AI capability calls through Hydracept only.

The Hydracept Public API runs external AI capabilities, such as image.generate.v1, through one interface with durable jobs, receipts, and bring-your-own-key provider credentials. You list and describe capabilities, quote a charge before running, then invoke a capability directly or submit it as a job that can be listed, streamed as events, approved, rejected, cancelled, and read back as a result, receipt, and downloadable artifacts. Around that core it manages project model adapters and LoRA weights with stable aliases, multi-provider comparisons, pinned inference receipts and provenance manifests, webhook delivery endpoints with replay, provider connections and organization credentials, storage backends, projects, and a prepaid billing wallet.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

94%

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

60%

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.

75%

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

35%

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.

54%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A-Signals: 1

75%

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: D+Signals: 1

47%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Hydracept Public API to your agent

Capabilities

Start building with Hydracept Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Hydracept Public API

Jentic AI Readiness Score

Hydracept 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