Install
Every way of using Antseed runs a local buyer that discovers sellers and pays them. Pick how you want to reach it:
- Gateway: API keys, budgets and a web console. Recommended.
- Desktop app: one person, a UI, and one-click setup for local coding tools.
- CLI: the bare buyer proxy for scripts and headless machines.
Gateway
The gateway ships in the Antseed CLI. You can run it on your own computer or install it on a Linux server.
On your computer
On macOS or Linux (including WSL), install the CLI, start the gateway in the background and get a console setup link with one command:
curl -fsSL https://antseed.com/install.sh | bash
It needs Node.js 20 or later (on macOS with Homebrew it installs Node.js for you), installs @antseed/cli with npm without sudo, logs to ~/.antseed/gateway.log and prints how to stop the gateway. Set ANTSEED_CLI_VERSION to install a specific CLI version. Read the script before running it.
On Linux with systemd you get this install from a desktop session or WSL. Elsewhere, for example over SSH, install.sh runs the server installer instead. Add --local to force the install for your user: curl -fsSL https://antseed.com/install.sh | bash -s -- --local.
Or install the CLI (Node.js 20 or later) yourself, then start the gateway:
npm install -g @antseed/cli
antseed gateway start
This starts a buyer on port 8377 and the gateway on http://localhost:8379, with its API at http://localhost:8379/v1 and the console at http://localhost:8379/console. Pass --no-buyer if you already run a buyer yourself. To run it in the background instead, starting at login and restarting if it stops, use antseed gateway service install (a launchd agent on macOS, a systemd user service on Linux, no root).
The console has no owner yet. Get a one-time setup link, open it, and register a passkey or connect a wallet to become the owner:
antseed gateway console-link
A gateway on your computer only works while the computer is on and is not reachable from other machines. To share it, publish it with a tunnel endpoint or move it to a server.
On a server
One command installs the buyer and the gateway as systemd services on a Linux server and can publish them over HTTPS:
curl -fsSL https://antseed.com/install.sh | bash -s -- --domain gateway.example.com
On Linux with systemd, install.sh runs the server installer as root when you pass an option such as --domain, or when there is no desktop session (over SSH, or from cloud-init). Add --server to force it. See Run a gateway on a server.
Next: Quickstart.
Desktop app
Antseed Desktop bundles a local gateway, a chat, and identity storage in the operating system keychain. Download it from antseed.com or the latest release page.
- macOS:
.dmgfor Apple Silicon and Intel, signed and notarized. - Windows:
.exeinstaller for x64, code-signed. - Linux:
.AppImageand.deb.
No account is needed. Free models work right away; for paid models, add funds by card or USDC from Add funds on the app's Home.
Next: Desktop app.
CLI
The CLI needs Node.js 20 or later and runs on macOS, Linux and Windows.
npm install -g @antseed/cli
antseed --version
antseed update installs newer versions later; see Updating.
Start the local buyer proxy:
antseed buyer start
It listens on http://localhost:8377. Free models need nothing else. For paid models, run antseed buyer deposit to get a funding address and QR code for USDC on Base.
Next: Use the local buyer proxy. To serve AI instead, see Become a provider.
Identity
Your node identity is one secp256k1 private key. Its EVM address is your peer id on the network and the wallet your payments come from.
On first run the CLI creates the key at ~/.antseed/identity.key. On servers, pass it from a secrets manager with ANTSEED_IDENTITY_HEX, or encrypt the key file with a passphrase; see Protecting wallet keys. To keep several buyers apart, give each its own data directory; see Buyer configuration.
Back up your identity key. Losing it means losing the funds and history tied to that address.