KAEL Endpoints

KAEL uses several public web surfaces. This page maps their responsibilities; use KAEL API for the HTTP contract.

chat.aethex.tech

Purpose: public conversational client.

Current responsibilities:

• Stream KAEL responses.
• Maintain a browser session.
• Offer sign-in when configured.
• Expose history, memory, model, and profile controls supported by the API.
• Route users toward relevant AeThex resources.

Open KAEL Chat

kael.aethex.tech

Purpose: dedicated KAEL identity and system surface.

This surface presents KAEL as an AeThex system and can expose deeper operator-oriented or experimental interfaces according to the viewer’s authorization.

Open KAEL

api.aethex.tech

Purpose: KAEL and AeThex API runtime.

Public endpoint groups include:

• Health and discovery.
• Chat and SSE streaming.
• Authentication.
• History and memory.
• Identity and profile summaries.
• Generated documents and feeds.
• Signed integration entry points.

Check API health

docs.aethex.support

Purpose: durable operating documentation and public API reference.

The docs describe stable behavior, maturity, security boundaries, and integration workflows. They are not an operator console.

aethex.support

Purpose: user-facing support routing.

Use support when a user needs assistance, incident routing, or clarification that is not resolved by the docs.

Related documentation