Environment Variables

NPL local / CI

No secrets required for the reference evaluator:

npx @hardalion/npl-policy-engine --tool drop_table --json

Optional: point at a custom policy file with --policy-file ./policy.yaml.

API platform integrators

When building a client that calls api.hardalion.com:

Variable	Purpose
`HARDALION_API_KEY`	Your `hdl_test_` or `hdl_live_` key (never commit)
`HARDALION_API_BASE`	Default `https://api.hardalion.com`
`HARDALION_TENANT_ID`	Workspace tenant ID for SDK wrap
`HARDALION_AGENT_ID`	Registered agent ID for AgentIAM

Example:

curl -H "Authorization: Bearer $HARDALION_API_KEY" \
  https://api.hardalion.com/v1/agents

Create keys in the Developer portal.

Nexus dashboard (tenant API)

For console-automation or tenant-scoped exports:

Variable	Purpose
`NEXUS_API_KEY`	Tenant key (`hnx_live_…`)
`NEXUS_API_BASE`	Default `https://nexus.hardalion.com`

Shadow and enforce mode

No extra env vars required. Toggle via API:

curl -X PATCH "$HARDALION_API_BASE/api/v1/execution-mode" \
  -H "Authorization: Bearer $HARDALION_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"execution_mode":"shadow"}'

Generating secrets (for your own apps)

node -e "console.log(require('crypto').randomBytes(32).toString('hex'))"