Create a feature engineering proposal
Start a CrewAI run that designs features and a CTAS query.
NexusOne publishes Crew events under the job’s UUID. The portal polls
/api/events/{job_id}. The response carries that ID as X-Correlation-ID.
Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Body
Top-level request to start a feature engineering proposal.
Fully qualified output table. For example iceberg.automl_credit_risk.training_v1. Schema must be under the AutoML namespace.
Natural-language description of the prediction problem.
Fully qualified source tables in catalog.schema.table format.
1Columns that uniquely identify a training row.
1How to derive the label column for the training table.
Provide exactly one of column or derivation. 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.
Response
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 more than 10 KB of JSON when this grows with per-column null rates and sample rows. That often exceeds output-token limits. Run the SQL directly to inspect rows. Only persist what's cheap and structurally useful.

