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

# Llms cli section

## Para CLI (`@getpara/cli`)

The Para CLI is a developer tool for managing API keys, organizations, projects, and configuration from the terminal.

### Installation

```bash theme={null}
npm install -g @getpara/cli
```

### Authentication

```bash theme={null}
para login          # OAuth browser flow with PKCE
para logout         # Clear stored credentials
para auth status    # Check session validity (server-side)
para whoami         # Show user, org, project, environment
```

Sessions are stored at `~/.config/para/credentials.json` (0600 permissions). PROD and BETA share the same developer portal session.

### Configuration

```bash theme={null}
para config get [key]         # Read config values
para config set <key> <value> # Set config value
para config unset <key>       # Remove config value
para init                     # Create .pararc in current directory
```

Resolution order: CLI flags → environment variables (`PARA_ENVIRONMENT`, `PARA_ORG_ID`, `PARA_PROJECT_ID`) → `.pararc` → global config → defaults.

### Organizations & Projects

```bash theme={null}
para orgs list                    # List organizations
para orgs switch [org-id]         # Switch active org
para projects list                # List projects
para projects switch [project-id] # Switch active project
para projects create              # Create project (-n, --framework)
para projects update [project-id] # Update project
para projects archive [project-id]# Archive project (keys stop immediately)
para projects restore <project-id># Restore archived project
```

### API Keys

```bash theme={null}
para keys list                   # List API keys
para keys get <key-id>           # Get key details (--show-secret, --copy)
para keys create                 # Create key (-n, --display-name)
para keys rotate <key-id>        # Rotate key (--secret for secret key)
para keys archive <key-id>       # Revoke key
para keys config [key-id]        # Configure key settings
```

`para keys config` sub-commands: `security`, `branding`, `setup`, `ramps`, `webhooks`. Each accepts flags for non-interactive use.

### Scaffold a Project

```bash theme={null}
para create [app-name]   # Scaffold Next.js or Expo app with Para SDK
```

Templates: `nextjs`, `expo`. Supports `--networks`, `--email`, `--phone`, `--oauth`, `--wallets`, `--bundle-id`, `--package-manager`, `-y` for non-interactive mode.

### Diagnostics

```bash theme={null}
para doctor [path]       # Scan for SDK integration issues
```

Checks: API key env var, env var prefix, CSS import, ParaProvider, duplicate ParaModal instances, QueryClient, "use client" directive, version consistency, chain dependencies, deprecated packages. Use `--json` for CI/CD (exits 1 on errors).

### Global Flags

| Flag                | Description                                          |
| ------------------- | ---------------------------------------------------- |
| `-e, --environment` | Target environment: `DEV`, `SANDBOX`, `BETA`, `PROD` |
| `--org <id>`        | Override active organization                         |
| `--project <id>`    | Override active project                              |
| `--json`            | Output as JSON                                       |
| `--quiet`           | Suppress non-essential output                        |
| `--no-input`        | Disable interactive prompts                          |

### CLI Documentation

See the CLI entries in the Docs section above for full documentation links.