CLI

The Queria CLI command set and when to use each command

Command set

Command	Purpose
`queria list`	List datasets
`queria search <keyword>`	Keyword search across datasets, tables, and columns
`queria info <dataset>`	Dataset metadata (license, source, etc.)
`queria schema <dataset>`	List a dataset’s tables
`queria columns <dataset> [table]`	List columns (narrowed down when a table is given)
`queria summarize <table>`	Column statistics for a table (full scan)
`queria sql "<query>"`	Run SQL
`queria docs list`	List this documentation’s pages
`queria docs show <name>`	Print one documentation page in the terminal
`queria skills list / show <name>`	List and print the published agent skills
`queria skills install [name]`	Install the agent skills into this project or machine
`queria login / logout`	Log in with browser approval / delete the saved token
`queria auth set-token / status / clear`	Manage API tokens (relaxed rate limits)
`queria create / edit / delete`	Register one of your own datasets, change its visibility, or delete it
`queria init / pull / run / push / sync`	Build and publish one of your own datasets
`queria expire`	Drop snapshots past the retention period, and the data files they held
`queria validate`	Check your own dataset’s declarations against your local data
`queria compile`	Write `dataset.json` from the declarations and your local data
`queria mcp`	Start the stdio MCP server
`queria telemetry status / disable / enable`	Manage anonymous usage telemetry
`queria feedback send / status / allow / disallow`	Send a request or a problem report, and set whether agents may send

Output formats

Choose the stdout format with --format:

table (default) — a formatted table for humans
csv — CSV with a header
json — a JSON array of records
jsonl — one JSON record per line (for stream processing)
markdown — a Markdown table (for pasting into docs and articles)

queria list --format json | jq '.[].datasource'

table favors readability: newlines inside a value are folded to spaces. A value too wide for the terminal is wrapped onto further lines rather than cut off. Set a width with COLUMNS=200 queria ... to change where it wraps. Piped or redirected output is not wrapped and stays on one line per row.

File export

Write results to a file with --out. The extension determines the format (.parquet / .csv / .json / .jsonl). For large results, use --out instead of stdout.

queria sql "SELECT * FROM e_stat.ssds.a_pref_population" --out pop.parquet

Automatic dataset ATTACH

When sql references <dataset>.<schema>.<table>, any dataset not yet connected is attached automatically. In cases where auto-detection doesn’t kick in — such as querying information_schema — specify datasets explicitly with --datasets:

queria sql "SELECT * FROM information_schema.tables WHERE table_catalog = 'jma'" --datasets jma

When two accounts publish the same dataset name, write the handle as well: --datasets alice/sales. The name you use in SQL is still the short one (sales.main.…). To query your own private datasets, run queria login first or pass QUERIA_TOKEN.

API tokens

Public data on data.queria.io works without a token, but rate limits apply. Registering a token raises the limits and lets you query your own private datasets.

On a personal machine, queria login is the easiest way. Approve in the browser and the token is issued and saved:

queria login

For non-interactive environments such as CI and BI tools, issue a token at queria.io/settings/tokens and pass it with queria auth set-token <token> or the QUERIA_TOKEN environment variable. See Authentication for details.

Feedback

From the terminal, queria feedback send sends dataset requests, data problems, and documentation errors. The full text of what will be sent is shown before it goes. See Telemetry for details.

queria feedback send "I need childcare waiting-list counts by municipality" --kind dataset_request

Bug reports and feature requests are also welcome as issues.