Adaption Labs Introduces 'Invent a Dataset': Training Data Generated From a Task Description, Not a Seed Corpus
Adaption Labs released "Invent a Dataset," a feature that generates structured, training-ready datasets from natural language behavior descriptions without requiring a seed corpus, predefined schema, or labeling guide The API uses domain codes (e.g., medical, medical.symptoms_diagnosis) as primary controls, with async generation via datasets.invent and datasets.get polling Two output formats are supported: instruction_dataset (prompt-completion pairs for SFT) and preference_pairs (chosen/rejecte
Analysis
TL;DR
- Adaption Labs released "Invent a Dataset," a feature that generates structured, training-ready datasets from natural language behavior descriptions without requiring a seed corpus, predefined schema, or labeling guide
- The API uses domain codes (e.g., medical, medical.symptoms_diagnosis) as primary controls, with async generation via datasets.invent and datasets.get polling
- Two output formats are supported: instruction_dataset (prompt-completion pairs for SFT) and preference_pairs (chosen/rejected pairs for DPO-style training)
- Language expansion supports both translate and localize modes, with sample_rate control and credit billing on expanded output rows
- Dataset IDs integrate directly with AutoScientist (launched May 2026), which co-optimizes data and training recipes, reportedly beating human-configured training by 35% across eight verticals with win rates improving from 48% to 64%
Why It Matters
This represents a significant shift in the synthetic data pipeline by eliminating the need for existing seed data or manual schema design, allowing practitioners to generate training data directly from behavioral intent. The tight integration between data generation and AutoScientist's co-optimized training creates a closed-loop system that could substantially reduce the time and expertise required to produce domain-specialized models. For organizations working with proprietary or specialized tasks where relevant data is scattered across internal systems, this approach bypasses the traditional bottleneck of data collection and labeling.
Technical Details
- API Mechanics: A single
datasets.inventcall initiates async generation; status is polled viadatasets.getuntilsucceededorfailed. Theestimate=Trueparameter allows cost previewing without charges. Anidempotency_key(up to 255 characters) ensures safe network retries. - Domain Control: Domain codes are fetched dynamically via
datasets.invent_domainsrather than hardcoded. Subdomain narrowing (e.g.,medical.symptoms_diagnosis) is supported, and multiple domains can be combined in a single run. - Output Formats & Ports: Data downloads as JSONL, JSON, CSV, or Parquet. The
instruction_datasetformat produces SFT-ready prompt-completion pairs, whilepreference_pairsgenerates chosen/rejected pairs for preference optimization like DPO. - Language Expansion: Two modes—
translate(language variants) andlocalize(country-language pairs with locale-specific wording). Asample_rateparameter (0.01–1) controls expansion fraction, with credits billed on expanded row count. - AutoScientist Integration: Dataset IDs feed directly into
autoscientist.create, which co-optimizes data and training recipes. Evaluated across eight verticals with 5,000–100,000 row datasets on Together AI fine-tuning architectures, showing 35% average improvement and win rate gains from 48% to 64% versus staff-configured training.
Industry Insight
The "zero-data loop" paradigm—generating data from intent and immediately feeding it into co-optimized training—could become a standard workflow for vertical AI development, particularly in regulated or specialized domains where labeled data is scarce or proprietary. Practitioners should evaluate whether the hosted-only generation model (no self-hosted path documented) aligns with data governance requirements, especially for sensitive domains like healthcare. The reported 35% improvement over human-configured training suggests that automated data-train co-optimization may soon outperform traditional manual pipeline design, making it worth benchmarking against existing fine-tuning workflows before committing to custom data collection efforts.
Disclaimer: The above content is generated by AI and is for reference only.