Get started

Three tracks cover the same ground: the app, where you click; the command line, one command per step; and Claude, where you say what you want and the MCP server does it. Pick the one you live in.

Before you start

• The app, at , on Base Sepolia (chain id 84532), where the dollar is zUSD and the faucet gives ZAI and zUSD once per wallet. On your own machine, scripts/devstack.sh review from the repository root starts a private copy instead: the local development network (chain id 31337, RPC http://127.0.0.1:8545) with fifty demo services.
• A wallet in the browser for the app's staking steps; a private key in AIOUM_PRIVATE_KEY for the same steps from the command line or from Claude. Agents and selling need neither.
• The repository checked out and scripts/devstack.sh setup run once: it builds the contracts and every package (the CLI and the MCP server included), then boots the whole local network: the chain, fifty real services and every one a key in .env unlocks (.env.example lists them), the agent runner, your private node, the app and the docs. scripts/devstack.sh update pulls the latest, rebuilds and restarts it.

Add your keys

Every key the network runs on is one list on your machine: http://127.0.0.1:8590, up with the rest of scripts/devstack.sh review (or npm run keys:console in offchain/). Each row is a key, grouped by what it unlocks: the listings it turns on, expandable, with the ones live right now marked; where to get it; whether it is required, recommended or optional; whether it is set; and where it belongs: server for the network's own services and every catalogue key, local for your private node's OAuth client and connectors, either for what both use. Paste the key and Save: it goes into .env at the repository root, readable by you alone, and is never shown again. Apply restarts only what reads it, the catalogue rebuilt first, and reports each service as it comes back. A key nobody has to type: the wallet keys the local development network derives from its test mnemonic stay empty here and go into the server's .env before deploy.

Start

In the app the first thing you meet is Start here, four steps in order: your private node (installed with one command, on this device or on a server), what it connects to (a model, your accounts, your data, a wallet with caps), the network (the runner sees it: a green Connected), then your first job. Launch then takes anything you build step by step, and My Agents keeps every agent's record. In the app walks through them with the screens.

The three tracks

The three tracks share one order, so a step you did in one place is one command or one sentence in the others.

Next: In the app — Start, then seven walkthroughs with the screens shown and the buttons marked.