Authentication
The CLI authenticates against api.prxy.monster using an API token — the
same prxy_xxx key shape you’d pass in Authorization: Bearer ... from
your code.
Token paste (v0.1.0)
The only supported login flow today:
prxy login --token=prxy_xxxxxxxxxxxxxxxxOr interactively:
prxy login
# → Browser-based login is coming soon. For now, paste an API token.
# → Get one at https://app.prxy.monster/keys
# → Paste your prxy_xxx token: ********The token is verified by hitting GET /v1/users/me immediately after paste —
if it fails, nothing is written to disk.
Where to get a token
- Go to https://app.prxy.monster/keys
- Click Create key
- Copy the
prxy_xxxvalue (shown once — never displayed again) - Paste into
prxy login --token=<paste here>
You can also create a key from the CLI itself once you’ve logged in once:
prxy keys create ci-runnerBrowser-based login (v0.2.0+)
Coming soon. The plan:
prxy login
# → Opens https://app.prxy.monster/cli/auth?nonce=<nonce>
# → User logs in via Clerk
# → Dashboard exchanges nonce for a long-lived CLI-scoped token
# → CLI polls until the token arrives, saves to ~/.prxy/config.jsonToken paste will remain supported for CI / scripted use.
CI / scripted use
For non-interactive contexts, set the token via env var or pass it directly:
# Either:
export PRXY_TOKEN=prxy_xxx
prxy keys list
# (currently requires explicit login — env-var auth is a v0.2.0 follow-up)
# Or pre-seed the config file:
mkdir -p ~/.prxy
cat > ~/.prxy/config.json <<EOF
{ "endpoint": "https://api.prxy.monster", "token": "$PRXY_TOKEN" }
EOF
chmod 600 ~/.prxy/config.jsonA dedicated --token flag on every command (so you don’t need to round-trip
through the config file in CI) is planned for v0.2.0.
Multiple environments
The CLI persists a single endpoint at a time. To switch between staging and production, override the config dir:
PRXY_CONFIG_DIR=~/.prxy/staging prxy login --token=prxy_staging_xxx
PRXY_CONFIG_DIR=~/.prxy/staging prxy keys listA built-in prxy env use <name> is on the roadmap.
Logout
prxy logoutRemoves the config file entirely. Safe to run when not logged in (no-op).