Install
npm install -g @getpara/cli
You can also run the CLI without installing globally using npx @getpara/cli@latest, yarn dlx @getpara/cli@latest, or pnpm dlx @getpara/cli@latest.
Authenticate
Log in with your Para developer account:
This starts a Developer Portal sign-in flow and prints the browser instructions in your terminal. Once you approve, the CLI stores your session locally at ~/.config/para/credentials.json.
After login, the CLI automatically selects your first organization and project. Use para whoami to verify:
Configuration
The CLI resolves configuration from multiple sources in this order (highest priority first):
- CLI flags (
-e, --org, --project)
- Environment variables (
PARA_ENVIRONMENT, PARA_ORG_ID, PARA_PROJECT_ID)
- Project config (
.pararc in the current directory)
- Global config (
~/.config/para/config.json)
- Defaults (key environment:
beta)
Project-Level Config
Pin your organization, project, and environment to a directory with para init:
This creates a .pararc file in the current directory. Team members who clone the repo get the same defaults without manual setup. See the config commands page for details.
Use para init --yes when you already have the right org, project, and key environment selected and want to skip the environment prompt.
Global Config
Set defaults that apply across all projects:
para config set defaultEnvironment beta
para config set defaultOrganizationId your-org-id
para config set defaultProjectId your-project-id
Key Environment
Each Para project has two API key tiers: beta (for development and testing) and prod (for production). The -e flag selects which tier to operate on:
para keys list -e beta # List beta keys (default)
para keys list -e prod # List prod keys
| Key Environment | Description |
|---|
beta | Development and testing keys |
prod | Production keys |
beta. Most commands auto-resolve the correct API key from your active project and key environment, so you rarely need to pass a key ID explicitly.
Global Flags
These flags work with every command:
| Flag | Description |
|---|
-e, --environment <env> | Key environment: beta or prod (default: beta) |
--json | Output as JSON for scripting and CI/CD |
-q, --quiet | Suppress non-essential output |
--org <id> | Override the active organization |
--project <id> | Override the active project |
The CLI does not use a global no-input flag. Commands that can run non-interactively expose their own required flags, such as para init --yes, para keys rotate --yes, or para create my-app -t nextjs --networks evm.
Next Steps
