Teads lets AI agents orchestrate ML experiments via Datakinator MCP, yielding 5–10% model uplift and nearly $1M in margin gain
Even after Datakinator gained a UI, manually adding features or choosing hyperparameters still took several minutes and left room for human error; earlier, the platform required launching a Scala notebook on the cloud that took up to 15 minutes each time, limiting the team to a few hundred experiments a year.
The first agentic iteration relied only on existing API routes without enriched context, causing failures such as using the wrong date and referencing features that did not exist in specific datasets.
After enriching the MCP with context tools and adding cost guardrails, the agent enabled over 200 experiments in 48 hours, delivered up to a 5–10% uplift on offline metrics across multiple models, and translated to nearly a million in direct margin gain.
Show all 7 reported metrics
Frequently asked questions
What did this team achieve with this AI workflow?
After enriching the MCP with context tools and adding cost guardrails, the agent enabled over 200 experiments in 48 hours, delivered up to a 5–10% uplift on offline metrics across multiple models, and translated to ne…
What tools did this team use?
Datakinator, MCP, coding agent.
What results were reported?
Experiments started in 48 hours: more than 200 experiments; Offline metric uplift: 5–10%; Direct margin gain: nearly a million in direct margin gain; ROI headline: $1M ROI (source-reported, not independently verified).
What failed first in this deployment?
The first agentic iteration relied only on existing API routes without enriched context, causing failures such as using the wrong date and referencing features that did not exist in specific datasets.
How is this back office ops AI workflow structured?
Data scientist triggers agent → Context probing → Cost estimation and approval → Experiment execution → Failure correction loop.