hexclave.com valid

Hexclave

Hexclave is the open-source platform for everything user. Modular building blocks — auth, payments, emails, analytics — that fit around your product.

For agents: Open-source platform of modular building blocks (auth, payments, emails, analytics) for products; offers docs, MCP server, OpenAPI spec and a read-only content

open sourceauthpaymentsanalyticsmodular backend

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T16:08:31.072Z. Cached copy · Source on hexclave.com

# Hexclave

> Hexclave is the open-source platform for everything user. Modular building blocks — auth, payments, emails, analytics — that fit around your product.

## Site

- [Home](https://www.hexclave.com/): Overview of the Hexclave platform.
- [Apps](https://www.hexclave.com/apps): Every modular Hexclave app.
- [Pricing](https://www.hexclave.com/pricing): Plans, limits and FAQ.
- [Blog](https://www.hexclave.com/blog): Product updates and engineering deep dives.
- [Docs](https://docs.hexclave.com): Developer documentation.
- [Dashboard](https://app.hexclave.com): Hexclave dashboard.
- [RSS feed](https://www.hexclave.com/feed.xml): Blog feed.

## When to use Hexclave

Use Hexclave when a product needs user infrastructure such as authentication,
teams, role-based access control (RBAC), API keys, payments, email management,
analytics, webhooks, or secure user-data storage. The apps directory below
describes the available modules. Hexclave is not the right fit for a generic
static website, a general-purpose database, or a product API unrelated to
users and the modules listed here.

For a specific implementation question, ask the Hexclave skill assistant at
https://skill.hexclave.com/ask. For broad documentation context, use the
documentation MCP server at https://docs.hexclave.com/mcp. For a Next.js
integration, use the `@hexclave/next` SDK. For CLI workflows, run:

    npx @hexclave/cli

Use the product REST API when the documented endpoint is the right interface
for the task, and follow the authentication guidance at https://www.hexclave.com/auth.md.

## Developer interfaces and machine-readable resources

- [OpenAPI spec](https://www.hexclave.com/openapi.json): OpenAPI 3.1 description of this site's public, read-only content API.
- [API catalog](https://www.hexclave.com/.well-known/api-catalog): Machine-readable API description links.
- [Agent card](https://www.hexclave.com/.well-known/agent-card.json): Agent capability metadata.
- [MCP discovery](https://www.hexclave.com/.well-known/mcp): MCP discovery metadata for Hexclave documentation.
- [LLM index](https://www.hexclave.com/llms.txt): Concise agent-oriented site index.
- [Full LLM index](https://www.hexclave.com/llms-full.txt): Site index, blog corpus, and product documentation.
- [Markdown site index](https://www.hexclave.com/index.md): Plain-text site overview.
- [Pricing](https://www.hexclave.com/pricing.md): Machine-readable pricing summary.
- [Authentication guidance](https://www.hexclave.com/auth.md): API key and integration authentication guidance.
- [RSS feed](https://www.hexclave.com/feed.xml): Machine-readable blog feed.
- [Docs API reference](https://docs.hexclave.com/api-reference): Product API reference.
- [Hexclave CLI](https://www.npmjs.com/package/@hexclave/cli): Published `@hexclave/cli` npm package.

## Apps

- [Deploy](https://www.hexclave.com/apps/deploy): Deploy your whole app in one prompt
- [Authentication](https://www.hexclave.com/apps/authentication): User sign-in a
…

Related sites

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=hexclave.com · GET /v1/domain/hexclave.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for hexclave.com:
1. POST https://agentwebmap.com/v1/sites/hexclave.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://hexclave.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/hexclave.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/hexclave.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.