ZZ Stack — platform gateway

Every door below speaks MCP over streamable HTTP, and every MCP server
describes itself: connect and call tools/list to see exactly what it
offers, with each tool's arguments. Nothing here needs a manual.

https://api.165-232-169-165.nip.io/core/mcp
    zz-core — everyone
    The process layer: skills, your team's knowledge store, documents and their gates, the sources behind them, and where each initiative stands.
    auth: Bearer <your token>

https://api.165-232-169-165.nip.io/manage/mcp
    access (behind the ZZ Access agent) — the ZZ Access agent
    A person's own building-block keys, their own platform token, and their client setup. You do not wire this up yourself — talk to the ZZ Access agent, which is the one place access is managed.
    auth: Bearer <your token>

https://api.165-232-169-165.nip.io/admin/mcp
    platform admin — any member; each tool authorises per call
    People, teams, tokens, the flow registry, block grants, and the projections into every client the platform serves. Tools refuse callers who lack the authority.
    auth: Bearer <your token>

https://api.165-232-169-165.nip.io/p/<block>/mcp
    building blocks — teams granted that block
    A third-party platform, called with YOUR OWN key. Store the key first via /manage.
    auth: Bearer <your token>

https://api.165-232-169-165.nip.io/pkg/<client>.tgz
    client package — everyone, for their own
    Your access, rendered as an installable marketplace for Claude Code, Codex or Hermes: the platform baseline, the tools for your own keys and tokens, and one plugin per flow your teams installed — so you receive no block and no method you do not use. A flow you run only in a terminal travels whole; one you also run in a browser stays a pointer, so both places run the same method. Your CLAUDE.md / AGENTS.md / SOUL.md are never touched.
    auth: Bearer <your token>

https://api.165-232-169-165.nip.io/architecture
    what this platform is — everyone, no token
    The platform explained end to end: the lifecycle shape and one method filling it in, how the method is measured and improved, what is remembered, why a document can be trusted, and what it takes to move it elsewhere.
    auth: none — it describes the platform, and contains nothing from inside it

https://api.165-232-169-165.nip.io/app
    knowledge base — everyone
    Your team's documents in a browser: browse, search, and attach what someone said as a source. Documents themselves change only through their flow.
    auth: your token, pasted at the login screen

No token yet?
  Open the platform and pick the ZZ Access agent. Ask it for a token:
  it is shown once, carries your identity and your team's access, and
  you can revoke it yourself at any time. That same agent stores your
  keys for the building blocks and prints the setup for Claude Code,
  Codex or Hermes. One agent, everything about your access.