# Quickstart

> From install to a running agent microVM — log in, attach a card in the browser, provision, and connect.

Part of the jurniti developer docs — canonical page: https://www.jurniti.com/docs/quickstart · full docs index: https://www.jurniti.com/docs/llms.txt

## Your first run

Four steps take you from a fresh install to an agent running in its own
Firecracker microVM. Budget about five minutes; provisioning itself is ~3.

### 1. Log in

Authenticate this machine. The device flow prints a code and opens (or links)
a browser to confirm it:

```bash
jurniti login
```

Once you are in, `jurniti whoami`, `jurniti vms ls`, and `jurniti usage` all work
immediately — you only need a card to *provision*.

### 2. Add a card

```bash
jurniti billing add-card
```

> **Card entry is web-only:** `jurniti billing add-card` **opens your browser** to attach a payment method. Card details are entered on the web, into **Stripe's embedded fields (Stripe Elements)** — **never typed into the terminal**. The card goes straight to Stripe; the CLI and jurniti's servers never see or handle your card number. When the browser flow completes, come back to the terminal and continue.

Check it landed:

```bash
jurniti billing status
```

> **No free tier — a card is required to provision:** There is **no free trial and no free tier**. Bringing up a VM starts a real, billed Firecracker microVM, so a card must be on file first. What de-risks it is the **30-day money-back guarantee** on your first subscription: cancel within 30 days for a full refund, no questions asked.

### 3. Bring a VM up

Provision a paid VM for the harness (agent type) and plan you want. This charges
your saved card, then polls until the VM is running:

```bash
jurniti up --harness hermes --plan pro --cycle monthly
```

Not sure which harness? List them (and each one's auth requirement) with
`jurniti harnesses`.

### 4. Connect

Provisioning runs the moment payment clears (~3 minutes to a fresh shell). Then
find and open your VM:

```bash
jurniti vms ls           # find your new VM
jurniti vms get <id>     # its state, subdomain, and readiness
jurniti usage            # live VM counts + monthly spend
```

Each Pro/Max VM comes up on its own TLS subdomain. Open it, or drop into the
browser terminal from your dashboard.

> **Give your agent the same commands:** The CLI binary is also an MCP server. Mount it once and your own agent can run every verb above as a tool — see [MCP](/docs/mcp).