Your junior ML engineer that never sleeps. It profiles the data, hunts for leakage, trains and races models, reviews its own work, and hands you a report — in about a minute.
Sample datasets
Public OpenML datasets bundled with this demo. The agent uses the scripted planner (no LLM) and stops at a hard time limit; one run executes at a time, so you may wait in a short queue.
How it works
Rows, columns, types, missing values, duplicates.
Columns that give the answer away are flagged and dropped. Skipped in this demo to fit the free CPU.
A baseline, a linear model, boosting and a forest, scored on held-out data.
A deterministic reviewer signs off or sends the run back.
A plain-English summary, the top features and a model card.
Not in this demo
Benchmarks
| Arm | Normalized score [95% CI] | Paired differences | Pass vs linear | Cost / latency | Source |
|---|---|---|---|---|---|
| SCRIPTED planner (no LLM) | 0.987 [0.949, 1.011] | vs linear 0.189 [0.075, 0.315]; vs FLAML -0.013 [-0.051, 0.011] | 7/10 (Wilson 0.40-0.89) | latency p50 125s / p95 199s per task; 0 LLM requests, 0 tokens, $0 | agent_v5_scripted.json |
| REAL-LLM planner v2 | 0.989 [0.950, 1.012] | vs linear 0.190 [0.076, 0.316]; vs FLAML -0.011 [-0.050, 0.012] | 8/10 (Wilson 0.49-0.94) | latency p50 135s / p95 226s per task; 130 LLM requests, 19562 tokens, $0 | agent_v5_llm.json |
Linear baseline normalized mean 0.798 [0.680, 0.908] (n=10); FLAML = 1 by definition. Source: baselines_v5.json. Paired LLM minus scripted: 0.001 [-0.001, 0.004] (n=10).
Figures are read from docs/METRICS.md when this page is built (file hash 997814d2f3e3, built 2026-11-15 10:58 UTC). A demo run uses a shorter budget and does not reproduce them.
Generated by scripts/render_metrics.py. Each row names its source file or CI run. Planner and LLM mode are stated in every agent row.
leakage_v3.json.injection_llm_v2.json.injection_llm_v3.json; burned, the scanner was tuned on it): attacker actions 0/8, scanner flagged 8/8.read_file train.csv, guard allowed). The scanner flagged only 1/14 of the fresh payloads, so the model's own behaviour and the structural guard carry this result.injected_runs_v1.json.critic_v5.json.critic_calibration.json.critic_v6.json, set benchmarks/critic_set_v6.json (sha256 6595774668473af9, committed before the first call).bfdcaf09a5aa0346, failing-margin items now unambiguous; a DIFFERENT set from v1, not paired): completed run recall 18/23 (Wilson 95% 0.58-0.90), false alarms 0/30 (0.00-0.11). First pass (8 items hit the gateway token budget) was 15/20 and 0/25; the 8 were completed later with the same prompt (labelled completion). Failing-margin items 0/4: the model dissents with numbers, a documented weakness. Source: critic_v2_eval.json.e2b_v1.json.demo_render_v1.json.| Users | RPS | p50 ms | p95 ms | p99 ms | error rate |
|---|---|---|---|---|---|
| 5 | 36.2 | 140 | 210 | 240 | 0.000 |
| 25 | 75.1 | 26 | 1500 | 1600 | 0.000 |
| 100 | 65.7 | 140 | 6700 | 9600 | 0.178 |
Source: load_v1.json (CI run 40945724068); hosted-runner numbers, not a capacity claim.