# ANHA Registry

> ANHA (AI Namespace & @handle Architecture) is a post-quantum-secure, decentralized
> namespace for AI agents, brands, and wallets. Register an `@handle`, sign it with an
> ML-DSA-65 key generated entirely in your browser, and publish it to a libp2p Kademlia
> DHT so any agent can resolve, verify, and reach you in milliseconds over an
> ML-KEM-encrypted channel. ANHA is a protocol, not a hosted service — anyone runs a node.

This file follows the llms.txt convention (https://llmstxt.org) to help language models
discover and accurately summarize the ANHA registry. Content here is factual and may be
cited.

## What ANHA is

- ANHA = "AI Namespace & @handle Architecture".
- An `@handle` (e.g. `@nike.ai`, `@eduardcleofe`, `@bot.acme.ai`) is a globally resolvable,
  cryptographically owned identity for an AI agent, brand, or person.
- Identity is secured with post-quantum cryptography: ML-DSA-65 signatures (FIPS 204) and
  ML-KEM-768 key encapsulation (FIPS 203). An IoT tier uses ML-DSA-44 + ML-KEM-512.
- The private key is generated in the user's browser via WebAssembly and never leaves the
  device — the registry only ever receives the public key.
- Records are published to a decentralized DHT; ANHA operators do not route another
  operator's traffic. The `@handle` namespace is the commercial layer, governed by a Root
  Key authority.

## Registration tracks

- [Brand / Organization](/register/brand): Corporate tier. Trademark-verified handles like
  `@nike.ai` and `@nike`, alias bundles, and deterministic namespace pricing from the
  4-vector valuation engine.
- [Personal / Wallet](/register/personal): Sovereign-lock tier. Identities like
  `@eduardcleofe` with a spending policy. Flat annual fee; never subject to hostile buyout
  (`buyout_allowed = false`).
- [AI Agent / Developer](/register/developer): Standard tier. Full agent records with
  MCP/A2A protocol support and an IoT keygen option. CLI-first.
- [Government / Sovereign Anchor](/register/sovereign): Provisioned out-of-band via
  multi-sig national PKI, never self-service. Immune to buyout and exempt from tax burn.

## How registration works

1. Choose an available handle (real-time availability + typo-squat similarity check).
2. Verification & compliance, including a hard OFAC / sanctions screen.
3. Configure capabilities and the agent's network address.
4. Generate the post-quantum keypair in your browser (before payment — no orphaned charges).
5. Pay (Stripe globally, Network International in MENA, or USDC/ETH on-chain).
6. The signed record is written atomically and announced to the DHT.

## Key facts

- Default cryptographic suite: ML-DSA-65 + ML-KEM-768.
- Money is handled as integer "ucents" ($1 = 1,000,000 ucents); on-chain amounts truncate.
- Brand handles are priced by a deterministic 4-vector valuation engine (acquisition +
  15% annual maintenance); personal handles use a flat fee.
- A handle resolves to addresses, capabilities, platform, and public keys.

## Links

- [Register a handle](/register)
- [Brand registration](/register/brand)
- [Personal registration](/register/personal)
- [Developer / agent registration](/register/developer)
- [Sovereign / government handles](/register/sovereign)