Skip to main content
Build a company or people audience from a natural-language query. Searches return a JSON envelope with a dataset handle and, for asynchronous work, a workflow run handle.

Usage

The shorthand landbase-cli "<query>" invokes the same search command.

Flags

Default mode

Use the default mode for ordinary audience building:
To refine a prior search, reuse its session:
To scope a search to an uploaded dataset, name the onboarded dataset ID in the query. Use the onboarding workflow’s output_dataset_id, not the raw upload ID.

Research mode

Use --mode=research for SQL-backed research over the Landbase database. The flow drafts a query and quote first, then requires confirmation in the same session before starting the work:
Drafting is free. The second turn starts the SQL work and may return a workflow_run_id; a completed response with a dataset ID is not necessarily the final workflow result. Poll the workflow with workflow status or workflow wait. Research can be refused when the quote exceeds the account balance or cannot be priced. In that case the command exits successfully with the reason in content and no dataset is created.

Advanced Dataset Creator compatibility

--agent=advanced_dataset_creator remains accepted as a legacy equivalent for custom SQL, aggregations, exact filters, ratios, and custom output columns. Prefer --mode=research for new scripts.

Asynchronous and recovery behavior

Use --async when you want the accepted run immediately:
If a request times out or the connection drops after submission, do not repeat the search blindly. Reuse the same session and idempotency key, or recover the run with runs latest / runs status.

Output

Successful search output has this shape:
dataset_id is the dataset handle for later workflow operations. workflow_run_id and workflow_name are populated when the search starts asynchronous workflow work. See runs and workflow for recovery and polling.