ic-query

ic-query provides the icq executable for read-only Internet Computer metadata queries.

The 0.0.1 release starts with NNS metadata queries: registry version, subnet catalog lookup, node/provider/operator/data-center inventory, and topology reports.

Install

From this checkout:

make install

From crates.io after publication:

cargo install ic-query

Commands

icq nns registry version
icq nns subnet refresh
icq nns subnet list
icq nns subnet info <subnet|canister|subnet-prefix>
icq nns data-center list
icq nns node list
icq nns node-provider list
icq nns node-operator list
icq nns topology summary
icq nns topology coverage
icq nns topology versions
icq nns topology health
icq nns topology gaps
icq nns topology capacity
icq nns topology regions
icq nns topology providers

Most commands support text output by default and JSON output with --format json:

icq --network ic nns subnet info ryjl3-tyaaa-aaaaa-aaaba-cai --format json

Cache

The NNS subnet, node, provider, operator, data-center, and topology commands use project-local cache files under .icq/. Refresh commands fetch current mainnet registry data and replace the matching cache atomically:

icq nns subnet refresh
icq nns topology refresh

Subnet list/info commands require a cached subnet catalog and show an explicit refresh hint when it is missing. Node, provider, operator, and data-center list/info commands populate their component cache on first use. Refresh commands force a fresh fetch and replace the matching cache.

Development

This repository pins the local toolchain to Rust 1.96.0 while declaring Rust 1.91.0 as the crate MSRV.

make fmt-check
make clippy
make test
make package

The combined local gate is:

make ci

Integration

icq is a standalone metadata lookup tool. Orchestration, deployment, and application repositories can call the CLI when they need IC metadata instead of linking registry adapters directly. For one integration example, see Canic.

Status

0.0.1 is an initial extraction release. The command namespace is intentionally small:

nns is implemented.
sns is reserved for follow-up work.
Additional IC query families can be added without coupling query code to deployment tooling.