KAEL Endpoints
KAEL Endpoints documents the public KAEL-related web surfaces and what each one is supposed to represent.
Public surfaces
These domains should point users to the right KAEL experience without blurring their purpose.
chat.aethex.tech
Purpose: conversational entry point.
Use chat.aethex.tech for direct interaction with KAEL-style chat experiences. This surface should focus on conversation, guidance, support preparation, docs navigation, and user-facing assistant behavior.
Expected responsibilities:
- Let users ask questions in natural language.
- Explain AeThex concepts and docs.
- Help users find the right AeThex page or support path.
- Keep user-facing behavior clear and approachable.
kael.aethex.tech
Purpose: dedicated KAEL identity and system surface.
Use kael.aethex.tech as the KAEL-specific home for build notes, experiments, agent interface work, deeper system behavior, and future KAEL-specific workflows.
Expected responsibilities:
- Present KAEL as a named AeThex system.
- Host or link KAEL-specific experiments.
- Point to the changelog and docs.
- Separate KAEL system identity from general support or marketing pages.
Related AeThex surfaces
- docs.aethex.support — durable documentation and operating notes.
- aethex.support — support and help entry point.
- aethex.net — broader AeThex network/gateway presence.
Endpoint documentation checklist
For each KAEL surface, track:
- Current status.
- Intended audience.
- What users can do there today.
- What is experimental.
- Where bugs, support, or feedback should go.
Do not document private admin URLs, tokens, hidden endpoints, internal credentials, or unfinished privileged routes on public docs pages.