> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usealmanac.com/llms.txt
> Use this file to discover all available pages before exploring further.

# CLI

> Hosted Almanac commands for agents and technical users.

The CLI mirrors website product actions.

```bash theme={null}
almanac login
almanac orgs
almanac wikis
almanac create "Legal"
almanac use reverie/legal
almanac upload docs/
almanac garden --guidance "tighten stale pages"
almanac search "customer onboarding"
almanac show onboarding
almanac sources tree
almanac jobs wait last
almanac billing portal
almanac api-keys create "Local agent"
```

## Context

`almanac use <org>/<wiki>` stores the selected organization and wiki locally.
Commands that read or mutate a wiki use that selection.

```bash theme={null}
almanac use reverie/legal
almanac search "yc safe"
```

Use `--wiki <org>/<wiki>` when a command should target a different wiki.

```bash theme={null}
almanac search "yc safe" --wiki reverie/legal
```

## Product-only commands

Infrastructure setup does not belong in the user CLI. Users should see product
actions: login, create, upload, search, show, garden, jobs, sources, billing,
and API keys.

## API keys

API keys are organization credentials for SDK, MCP, and direct `/v1` access.

```bash theme={null}
almanac api-keys
almanac api-keys create "Read-only agent"
almanac api-keys create "Automation writer" --write
almanac api-keys delete ak_123
```

The default key can read/search. `--write` also grants wiki creation, source
upload, and garden job permissions. Almanac does not store key values; the full
secret is only shown once after creation.