Skip to main content
hiloop is pre-GA. The hosted edge (api.hiloop.ai) and the curl | sh installer are still being finalized — the flow below is what shipping looks like, and the API is versioned 0.x until GA.
Get from zero to a telemetry query in three steps.

​
1. Install the CLI

hiloop is a single static binary. 
curl -fsSL https://hiloop.ai/install.sh | sh
Verify it’s on your PATH: 
hiloop --version

​
2. Authenticate

The CLI sends a bearer token with every request; the hiloop edge authenticates it. Set your API key as an environment variable: 
export HILOOP_API_KEY="hil_…"
Confirm the API resolves your identity: 
hiloop whoami
This calls GET /v1/whoami and prints the org, tenant, and user the credential maps to — a quick auth sanity check.

​
3. Run a telemetry query

Telemetry is keyed by fork-tree node (see tree-native observability). Query a run with the generic API passthrough: 
hiloop api /v1/telemetry/query -X post -d '{
  "spec": {
    "runId": "<your-run-id>",
    "calculations": [{ "op": "CALCULATION_OP_COUNT" }]
  }
}'
The response is one row per breakdown group with the computed aggregations. See the API reference for the full QuerySpec (filters, breakdowns, time ranges) and the CLI reference for every command and flag.

​
Next steps

  • Concepts — sandboxes, forks, and tree-native observability.
  • CLI reference — the complete command surface.