Docs

Start Here · 01.03

Install Agentis and Boot the Local Runtime

Clone the repo, run pnpm install, and start the Agentis API on 127.0.0.1:3737 — then open the dashboard and mint your first API key.

InstallCLIpnpm

Clone and install

Clone & install dependencies
git clone <your-fork> agentis && cd agentis
pnpm install

This installs every package in the monorepo — the API runtime, the web dashboard, and the shared packages they both depend on — with a single pnpm workspace install. No separate database server setup, no Docker Compose file to reconcile first.

Boot the runtime

API only
pnpm dev              # API on http://127.0.0.1:3737
API + web dashboard together
pnpm dev:full         # API + web dashboard together

On first boot Agentis creates ./.agentis, initializes the SQLite schema, seeds an operator workspace, and generates the RS256 keypair it uses to sign JWTs — all automatically. There's nothing to run a migration tool for by hand.

Mint an API key

Open the dashboard, go to Settings → create an API key, and export it. Every example in these docs — every curl, every SDK call — authenticates the same way:

Every authenticated request
Authorization: Bearer $AGENTIS_API_KEY
API keys are hashed at rest — Agentis never stores or returns the raw key after you've copied it once. Treat it like a password.

Verify the install

Diagnose paths, adapters, and the database
pnpm doctor

Use this whenever something feels off after an install, an upgrade, or a machine move — it's the fastest way to confirm the data directory, detected model adapters, and database are all in a consistent state before you file a bug against your own setup.

Runtime up and key in hand, the next step is giving an agent a mind to think with: Bootstrap Your First Agent.

Continue