Install Jentic One Beta

Connect the Hexclave public content API to your agent

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

List the public Hexclave apps and read any one by its appId

List public blog posts from the Hexclave marketing site

Read site and agent resource metadata for the Hexclave site

Pull marketing-site content without any credential

Use Cases

Patterns agents use Hexclave public content API for, with concrete tasks.

GET STARTED

Start building with Hexclave public content API

Explore with Jentic One

View OpenAPI Document

★ Agent Access to Public Site Content

An AI agent building a view of Hexclave's offering calls the Hexclave public content API through Jentic to read the marketing site without any credential: it lists the public apps, fetches one by its appId, and pulls recent blog posts. Because the whole surface is read-only and unauthenticated, the agent can gather this content with no key to manage. Site and agent resource metadata tells the agent what else the site exposes.

List the public Hexclave apps, fetch one by appId, and pull the three most recent blog posts

Blog Content Syndication

A site or newsletter pulls Hexclave's public blog posts to syndicate or summarize them. The Hexclave public content API lists blog posts over a simple read-only HTTP GET, so an application fetches the latest marketing content directly. No authentication or account is required.

List the public blog posts and return the most recent one

Public App Directory Lookup

A directory or agent catalog reads the public apps Hexclave publishes and their details. The Hexclave public content API lists apps and returns a single app by its appId, all read-only, so an integration can mirror the public catalog. Site metadata rounds out what the agent can discover.

List the public apps and fetch the full details of one app by its appId

Key Endpoints

4 endpoints — the hexclave public content api serves the read-only content behind hexclave's marketing site: the public apps it lists, its blog posts, and site and agent resource metadata.

METHOD

PATH

DESCRIPTION

GET

/api/v1/apps

List public Hexclave apps

GET

/api/v1/apps/{appId}

Get a public Hexclave app by appId

GET

/api/v1/blog-posts

List public blog posts

GET

/api/v1/site

Get site and agent resource metadata

GET

/api/v1/apps

List public Hexclave apps

GET

/api/v1/apps/{appId}

Get a public Hexclave app by appId

GET

/api/v1/blog-posts

List public blog posts

GET

/api/v1/site

Get site and agent resource metadata

Why Jentic?

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

Setup

Wiring the Hexclave public content API by hand is light since it needs no credential, but you still build and maintain the HTTP calls to its apps, blog, and site endpoints. Through Jentic you install once, import it from the API Directory, and your agent calls it with no key to store.

Permission scoping

The Hexclave public content API is read-only and unauthenticated, so there is no token to over-scope. A Jentic rule can still limit your agent to just these content operations, so it reads apps and blog posts and touches nothing else you have connected.

Credential isolation

The Hexclave public content API needs no credential, so there is nothing to store. For the APIs you add that do use a key, Jentic stores it encrypted by your own Jentic One instance and injects it at execution time.

Intent-based discovery

Agents search Jentic by intent such as 'list public apps' or 'read blog posts', and Jentic returns the matching Hexclave operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Hexclave public content API through Jentic.

What authentication does the Hexclave public content API use?

The Hexclave public content API needs no authentication: every endpoint is a read-only public GET, per its OpenAPI spec. There is no key, token, or account to manage. Through Jentic you add it from the directory and your agent calls it directly, the same way you add APIs that do need a credential.

Can I read Hexclave apps and blog posts with the Hexclave public content API?

Yes. You list the public apps and fetch any one by its appId, and you list the public blog posts, all read-only. Site and agent resource metadata is available from a dedicated endpoint for discovery.

What are the rate limits for the Hexclave public content API?

The OpenAPI spec does not specify rate limits. For current limits, see the Hexclave documentation at https://www.hexclave.com.

How do I read Hexclave blog posts through Jentic?

Search Jentic with a query like 'read public blog posts', add the Hexclave public content API from the directory, and your agent calls the list-blog-posts operation directly, no credential needed. 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 Hexclave public content API?

Yes. The API is read-only and public, so an agent cannot change anything regardless, but a Jentic rule can still narrow it to just the operations you want, such as listing apps or blog posts, with every call logged. There are no write or destructive operations to worry about here.

Is there a Hexclave public content API MCP server?

You don't need an MCP server to give your agent the Hexclave public content API. Jentic connects it directly from the API Directory: import it and your agent calls the apps, blog, and site operations on demand without loading another server's tool definitions into its context.

Hexclave public content API

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingContent Managementnone4 EndpointsREST

For Agents

Read Hexclave's public marketing content over unauthenticated GET requests: list apps, fetch one by appId, list blog posts, and read site metadata. No key or account required.

Use for: List the public apps Hexclave publishes, Get the details of a Hexclave app by its appId, Retrieve the latest public blog posts from Hexclave, Read the Hexclave site and agent resource metadata

Not supported: Does not cover the authenticated Hexclave product API, write any content, or require a login. Use for reading public Hexclave marketing-site apps, blog posts, and site metadata only.

The Hexclave public content API serves the read-only content behind Hexclave's marketing site: the public apps it lists, its blog posts, and site and agent resource metadata. Every endpoint is an unauthenticated HTTP GET, so an application reads the site's public content without a key or account. It does not cover the authenticated Hexclave product API, which has its own reference.

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

99%

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.

50%

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

27%

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.

44%

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.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

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

84%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Hexclave public content API to your agent

Capabilities

Use Cases

Start building with Hexclave public content API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Hexclave public content API

Jentic AI Readiness Score

Hexclave public content 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