---
title: Configuration
description: "The amp CLI's global flags and environment variables, for setting the API host, output format, and request behavior."
product: general
token_estimate: 671
---
# Configuration

> For AI agents: a documentation index is available at [/docs/llms.txt](/docs/llms.txt). Append `.md` to any page URL for markdown, or send `Accept: text/markdown`.

These flags and environment variables control authentication, output, and API requests. Run `amp <command> --help` for the flags that a specific command accepts.

| Flag / env | Purpose |
| --- | --- |
| `--region <us|eu>` | Target the US or EU Developer API |
| `--base-url` / `AMP_API_BASE_URL` | API host (default: production) |
| `--env <env>` | Friendly environment name, mapped to a base URL |
| `--profile <name>` / `AMP_PROFILE` | Select a stored profile |
| `--token` / `AMP_TOKEN` / saved profile | Auth token |
| `--json` | Force raw JSON output (default when piped) |
| `--yes` | Skip confirmation for destructive operations |
| `--dry-run` | Preview supported DELETE commands |
| `--body-json '{...}'` | Merge extra JSON into request bodies |

## Base URL

`amp` defaults to production:

```text
https://developer-api.amplitude.com
```

Override it for staging or a local server, either with an environment variable or a flag:

```bash
export AMP_API_BASE_URL=http://localhost:3036
# or
amp --base-url http://localhost:3036 context
```

For normal authentication, use `--region us` or `--region eu`. The CLI still supports `--env` for `local`, `dev`, `staging`, `prod`, and `prod-eu`, and `--base-url` for an arbitrary host, but omits these development-oriented options from standard help. Don't pass `--region` and `--env` together.

## Output format

By default, `amp` prints human-friendly tables and summaries for list and context commands in an interactive terminal. Pipe the output to a file or another command, or pass `--json`, to get compact, raw API JSON instead. Scripts and agents should rely on `--json` rather than parsing table output.

Errors use a nonzero exit code and write a JSON error envelope to stderr. `amp help --json` prints the complete command catalog, and `amp <command> --help --json` prints one command's parameters.

The CLI rejects flags that don't apply to the selected command. When a misspelled flag closely matches a valid one, the error suggests the valid flag.

## Usage logging

`amp` doesn't collect client-side telemetry or send separate CLI telemetry events. The Developer API logs request metadata server-side to operate the service, including the route, HTTP status, account or organization, and CLI version.

## Auth precedence

`--profile`, `AMP_PROFILE`, `--token`, and `AMP_TOKEN` all affect which credential a command uses. For the full precedence order, go to [Authentication](https://amplitude.com/docs/developers/cli/authentication).