Start a CrewAI run that designs features and a CTAS query.
Documentation Index
Fetch the complete documentation index at: https://docs.nx1cloud.com/llms.txt
Use this file to discover all available pages before exploring further.
The access token received from the authorization server in the OAuth 2.0 flow.
Top-level request to start a feature engineering proposal.
Fully qualified output table, e.g. 'iceberg.automl_credit_risk.training_v1'. Schema must be under the AutoML namespace.
Natural-language description of the prediction problem.
Fully qualified source tables (catalog.schema.table).
1Columns that uniquely identify a training row.
1How to derive the label column for the training table.
Exactly one of column or derivation must be provided. column
refers to an existing column (or a simple SQL expression over source
columns). derivation is a natural-language description that the crew
translates into SQL.
DataHub domain or business domain for governance.
Username who owns the resulting training table.
Optional natural-language join guidance for the crew.
Crew run started; poll the job for the proposal.
The crew's proposal returned to the user for review.
Lifecycle of an AutoML feature engineering job.
running, pending_approval, failed, approved, materializing, complete Structured recipe describing the training table the crew designed.
The CREATE TABLE AS SELECT query the crew produced.
Result of running the CTAS query with a row limit during validation.
Kept intentionally lean — large agents produce >10KB JSON when this grows (per-column null rates, sample rows), and that often gets cut off by output-token limits. The user can run the SQL to inspect rows themselves; only persist what's cheap and structurally useful.