​
CLI

The Hilt CLI is for teams that want fast terminal workflows around the same objects the dashboard already uses. It is a public Hilt surface across the plan ladder, not a higher-tier add-on.

​
What the CLI is best at

Use it when you want:
  • quick merchant lookups from a terminal
  • repeatable scripts for support or operations
  • fast reads for products, members, or receipts
  • API key management without opening the dashboard every time

​
Install from Hilt

The supported public install path is the hosted Hilt release package: 
npm install -g https://www.hilt.so/downloads/hilt-cli-latest.tgz
If you want a pinned version instead of latest, install the versioned tarball: 
npm install -g https://www.hilt.so/downloads/hilt-cli-1.0.0.tgz

​
Verify the package checksum

curl -O https://www.hilt.so/downloads/hilt-cli-1.0.0.tgz
curl -O https://www.hilt.so/downloads/hilt-cli-1.0.0.tgz.sha256
sha256sum -c hilt-cli-1.0.0.tgz.sha256

​
Check the install

hilt --help

​
Build from source

Most teams should use the hosted Hilt package above. Build from source only if you are developing against a local Hilt environment or testing changes to the CLI itself. 
cd packages/cli
npm install
npm run build
npm link

​
Run it without linking globally

node packages/cli/dist/index.js --help
or: 
npm exec --workspace=packages/cli hilt -- --help

​
Authentication commands

hilt login
hilt login --email merchant@example.com
hilt login --token EXISTING_TOKEN
hilt whoami
hilt logout

​
What those commands do

CommandPurpose
hilt loginInteractive login with email and password
hilt login --emailPre-fills the email prompt
hilt login --tokenStores an existing token after verifying it
hilt whoamiShows the current authenticated user
hilt logoutClears the stored token

​
Top-level help

hilt --help
Representative output: 
Usage: hilt [options] [command]

Hilt Pay CLI

Options:
  -v, --version    Print the current version
  -h, --help       Show help

Commands:
  login [options]  Authenticate with Hilt and store your session token
  logout           Clear the stored session token
  whoami           Show the currently authenticated user
  keys             Manage API keys for Hilt Pay integrations
  pay              Hilt Pay merchant lookup and support workflows

​
Key management commands

hilt keys list
hilt keys create --name "Production integration"
hilt keys create --name "Sandbox checks" --sandbox
hilt keys revoke KEY_ID
The --sandbox flag does not create a separate fake checkout network or a full test environment. Today it is best used to label lower-risk internal tooling or pre-launch API usage inside a real merchant workspace. If you want to validate the full payment, membership, receipt, and support trail, use one tiny live payment instead.

​
Key command options

CommandUseful options
hilt keys list--json
hilt keys create--name, --sandbox, --json
hilt keys revoke KEY_IDnone
The raw key is shown once on creation. Store it immediately.

​
Product commands

hilt pay products list
hilt pay products list --status ACTIVE
hilt pay products list --type PAYMENT_LINK
hilt pay products get PRODUCT_ID
hilt pay products archive PRODUCT_ID

​
Product command options

CommandUseful options
hilt pay products list--status, --type, --limit, --offset, --json
hilt pay products get PRODUCT_ID--json
hilt pay products archive PRODUCT_IDnone

​
Membership commands

hilt pay members list
hilt pay members list --product PRODUCT_ID
hilt pay members list --status ACTIVE
hilt pay members lookup --wallet WALLET_ADDRESS
hilt pay members lookup --identity BUYER_IDENTITY
hilt pay members lookup --tx TX_SIGNATURE
hilt pay members get MEMBERSHIP_ID

​
Membership command options

CommandUseful options
hilt pay members list--product, --status, --platform, --limit, --offset, --json
hilt pay members lookup--product, --wallet, --identity, --tx, --json
hilt pay members get MEMBERSHIP_ID--json

​
Receipt commands

hilt pay receipts list
hilt pay receipts list --page 1 --per-page 20
hilt pay receipts list --wallet WALLET_ADDRESS
hilt pay receipts get RECEIPT_ID

​
Receipt command options

CommandUseful options
hilt pay receipts list--page, --per-page, --wallet, --json
hilt pay receipts get RECEIPT_ID--json

​
Useful flags

  • --json for raw JSON output on data commands
  • -h, --help for command help
  • -v, --version for version output

​
Command-to-route map

CLI commandAPI route
hilt keys listGET /v1/keys
hilt keys createPOST /v1/keys
hilt keys revokeDELETE /v1/keys/{key_id}
hilt pay products listGET /v1/products
hilt pay products getGET /v1/products/{product_id}
hilt pay products archiveDELETE /v1/products/{product_id}
hilt pay members listGET /v1/memberships
hilt pay members lookupGET /v1/memberships/lookup
hilt pay members getGET /v1/memberships/{membership_id}
hilt pay receipts listGET /v1/receipts
hilt pay receipts getGET /v1/receipt/{receipt_id}

​
Example help flow

hilt --help
hilt keys --help
hilt pay members lookup --help

​
Environment variable

HILT_API_URL=https://api.hilt.so
Use that to point the CLI at a different API base URL when needed.

​
A reliable support flow in the terminal

hilt pay members lookup --identity @buyer
hilt pay receipts list --wallet WALLET_ADDRESS
hilt pay receipts get RECEIPT_ID
That pattern usually gets you from a buyer complaint to the right proof trail quickly.

​
Current scope

The CLI is strongest for:
  • auth
  • key management
  • product inspection
  • membership lookup
  • receipt retrieval
The dashboard is still the best place to shape a new offer visually, but once the workspace is live the CLI is the fastest way to inspect and support it.