hexaeight.com valid

HexaEight

An AI agent with its own identity, running on your own machine. Every party — a person, an agent,

For agents: HexaEight: an AI agent with its own identity that runs on your own machine, with memories, missions and end-to-end encrypted agent-to-agent messaging. Docs cove

ai agentagent identityend-to-end encryptionlocal agentagent memory

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T13:20:25.257Z. Cached copy · Source on hexaeight.com

# HexaEight

> An AI agent with its own identity, running on your own machine. Every party — a person, an agent,
> a service — gets a cryptographic identity; every message between them is encrypted end to end and
> proves who sent it. No API keys, no certificates, no key exchange, and the recipient need not be
> online.

This is the machine-readable index. If you are an agent helping someone install or integrate
HexaEight, read the sections in the order given: each assumes the one before it.

## What it is, in one paragraph

An **agent** is a running identity on its owner's machine. It proves who is calling, decides whether
they are allowed, and hands the work to an **engine** — usually the built-in **harness** (memories,
missions and a tool loop, run in a sandbox), or a process you wrote, which the agent runs with an
argv you declared. Agents never hold model credentials; they ask a **router** for a named route, and
the router holds the keys and decides who may use which model. Identity lives on the owner's phone,
in the **Authenticator**, and every agent is a **resource** assigned to a person's identity — which
is what puts a provable person behind it. People use an agent through the **workspace**, a browser
interface served from the same machine.

## Facts an integration usually needs

- The one-command installer sets up the licence, a router, the agent, the workspace and start at
  login: `curl -fsSL https://raw.githubusercontent.com/HexaEightTeam/hbia-agent/main/install.sh | bash`,
  run twice from an interactive terminal. Folders: `~/hbia-agent` (licence only), `~/heia-router`,
  `~/heia-agent`. Ports: 5100 router, 8770 agent, 5620 workspace. Manage with
  `heia status|restart|logs`.
- Identity files are `env-file` and `hexaeight.mac`, both **machine-bound**. Never copy them to
  another machine; hardlink them when one machine needs them in two folders.
- A resource's **password, licence code and `hexaeight.mac` are tied together**. The password
  cannot be changed. Encrypting or decrypting needs the identity, the password AND the ASK.
- **Until the first policy rule exists, nothing is enforced.** `0 policy rule(s) in force` at boot
  means the door is open. The installer writes a baseline that admits only the owner.
- A person appears in policy as `sha512(their email)`, never the address.
- The router's only config file is `upstreams.yaml`; it holds the upstreams *and* settings such as
  `requireIdentifiedCaller`. There is no `router.yaml`.
- Start order is **router, then agent, then workspace**. An agent started first reports a licence
  error that has nothing to do with the licence.
- On Windows, run everything under WSL.
- A **memory** is how an agent reaches information: documents, an API, or another agent
  (`connect-to-agent`), searched by name.
- A **mission** is a written method the agent follows: a flowchart of capability cards, a fence,
  optionally files it carries and a command set sealed in the agent. A **direct** mission hand
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=hexaeight.com · GET /v1/domain/hexaeight.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 hexaeight.com:
1. POST https://agentwebmap.com/v1/sites/hexaeight.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://hexaeight.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/hexaeight.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/hexaeight.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.