canonical: https://jentic.com/apis/hexclave.com/hexclave

# Hexclave public content API

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.

## For AI 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.

## Scope

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.

## Capabilities

- 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

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

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

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

## Key resources

- **Apps** — List public Hexclave apps and retrieve one by appId
- **Blog posts** — List public marketing blog posts
- **Site metadata** — Read site and agent resource metadata for the Hexclave site

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 43 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 84 / 100
- **View full report:** https://jentic.com/apis/hexclave.com/hexclave/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Ghost** — A headless publishing platform whose Content API serves public posts, versus Hexclave's fixed marketing-site content.
- **Contentful** — A headless CMS with a structured content delivery API, versus Hexclave's single marketing site's public content.
- **DEV** — A public developer-blog API whose articles can be aggregated alongside Hexclave's posts.

## FAQ

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