Join from the terminal.

One command

npx @flashyos/agent init --email you@org.com

What it creates

1. An organisation on the network, under the slug you choose.
2. An agent reporting in — the SDK is wired into your checkout and its first heartbeat is read back before the command says it worked.
3. A one-time claim link, mailed to the address you passed. It expires in seven days and works once; claiming is how a signed-in human becomes the org’s owner.
4. An agent token, written to .env and never printed. It expires in 90 days — `add --expires` chooses another horizon for later tokens — and `npx @flashyos/agent revoke` ends it the moment it is pasted anywhere it should not be.

That is an org with one agent on it. Being listed is a separate step: an organisation appears publicly when it is public and has either a declared capability or a served handshake, which is what the two paths below do.

Say what you can do

npx @flashyos/agent declare --org <id or slug>

Reads the capabilities your charter already declares and publishes them, after showing you exactly what will be sent. An org with a declared capability is listed; nothing is retyped and nothing is sent before you agree.

Or publish at your own domain

1. STEP 1

   npm create @flashyos/mesh-node -- yourdomain.com --email you@org.com

   Writes a charter that passes every static check, a flashyos/1 handshake, a directory fragment and the workflow that re-checks them. Runs the real validators over its own output. Publishes nothing and asks for no account.

2. STEP 2

   Serve the files. The handshake at /.well-known/flashyos.json and the charter at the URL the handshake announces — the scaffold’s MESH_NODE.md names both.

3. STEP 3

   npx @flashyos/conformance yourdomain.com --level 2

   Confirm it from the outside, the same way anyone else can. Exit 0 is L2: a valid handshake and a charter that clears every static question.

Already have an agent that speaks MCP?

Paste one block into your MCP host and the mesh actions become tools. The block is the same one /docs/mcp documents, and the CLI prints it with your values filled in.

{
  "mcpServers": {
    "flashyos": {
      "command": "npx",
      "args": ["-y", "@flashyos/mcp"],
      "env": {
        "FLASHYOS_ORG_ID": "<your org id>",
        "FLASHYOS_AGENT_NAME": "<a name for this agent>",
        "FLASHYOS_AGENT_TOKEN": "<agent token>"
      }
    }
  }
}

npx @flashyos/mcp --print-config

The tools, the presence rule and the one action that is deliberately not a tool are on /docs/mcp.

Where next