CLI

The meridian CLI covers the interactive side of the platform: managing resources, tailing events, simulating traffic, and tunneling webhooks to localhost. It's the fastest path for exploration and local development.

Install

npm install -g @meridian/cli
meridian --version   # 1.4.2

brew install meridian/tap/meridian

curl -sL https://get.meridian.dev | sh

Authenticate

meridian login              # opens the dashboard to mint a key
meridian login --key mrnd_test_…   # headless / CI

Credentials store in ~/.meridian/config.json. Profiles separate environments:

meridian login --profile prod --key mrnd_live_…
meridian --profile prod projects list

Command map

The local dev loop

meridian listen --forward localhost:3000/webhooks/meridian   # tunnel + log
meridian simulate event --type project.updated               # fire events
meridian events tail --project prj_9kLm2xVb7nQe              # watch the feed

meridian listen prints every delivery - payload, headers, your handler's response - the local delivery log.

Scripting

Every command takes --json for parseable output:

meridian projects list --json | jq '.[].id'
meridian api GET /v2/events --json | jq '.data[] | .type'

Exit codes: 0 success, 1 API error, 2 auth failure - composable in CI.

Configuration

{
  "default_profile": "dev",
  "profiles": {
    "dev":  { "key": "mrnd_test_…", "region": "us-east" },
    "prod": { "key": "mrnd_live_…", "region": "eu-west" }
  }
}

Flags override profile → env var (MERIDIAN_API_KEY) → config precedence.

When CLI vs SDK

• CLI: exploration, ops tasks, local dev, one-off scripts - human-driven.
• SDK: application code, automation, anything that runs unattended in production.