Mecka AI secures $60 million Series B for robot motion data

Mecka AI, a startup founded in 2024 that collects and analyses human-motion data for robot training, has raised a $60 million Series B led by Sequoia. Nvidia, Microsoft’s venture fund M12 and other investors also participated in the round.
The company is building a data supply operation for humanoid robots and other types of robots. It pays people to record themselves carrying out everyday tasks, including making coffee and repairing cars, while they wear body sensors and use smartphones.
Human demonstrations as robotics training material
Mecka AI’s stated ambition is to play a role in robotics comparable to that played in large language models by Scale AI, Mercor, Surge and other data-labeling businesses. Those companies provide the human-generated data from which LLM systems learn.
In Mecka AI’s model, the recordings capture human movement while a task is being completed. That makes the underlying dataset distinct from purely text-based labeling work and positions task demonstrations as a training input for robotic systems.
The financing follows reports that placed Mecka AI near a $500 million valuation. That context is reflected in Mecka AI’s reported $500 million valuation as the company moves from a reported prospective financing to an announced $60 million Series B.
A widening market for real-world robot data
Mecka AI is not alone in pursuing real-world datasets for robots. XDOF is another startup collecting training data and was reported to be in talks for a Series B at a $1.2 billion valuation.
Companies that first built human-data platforms for LLMs are also extending into robotics. Scale AI and Micro1 are among the businesses expanding their activity in that direction, placing Mecka AI in a field where data collection and analysis are becoming a defined part of the robotics supply chain.
Business implication
For organisations assessing robotic automation, Mecka AI’s funding underlines that a robot’s training data, and its fit with the tasks it must perform, should be evaluated alongside hardware, software and operational integration.
Mecka AI explained: role, evaluation and open questions
Mecka AI is building a data supply operation that records people performing real-world tasks and turns those demonstrations into training material for robots. The available information explains its position in the robotics data chain, but it does not establish pricing, customer deployments or integration requirements.
What Mecka AI does and how it fits into physical AI
Founded in 2024, Mecka AI collects and analyses human-motion data captured while people complete everyday tasks using body sensors and smartphones. In the physical AI ecosystem, this places the company at the training-data layer rather than establishing it as a robot manufacturer or deployment platform.
- Human demonstrations connect recorded movement with the completion of a specific task.
- The resulting data is intended to support training for humanoid and other robots.
- The supplied information does not define the available data formats, modalities or task catalogue.
Funding and reported valuation
Mecka AI announced a $60 million Series B led by Sequoia, with Nvidia, Microsoft’s venture fund M12 and other investors participating. Reports placed the company near a $500 million valuation. The funding amount and reported valuation describe different things and should not be treated as interchangeable figures.
- The announced Series B financing was $60 million.
- The reported valuation was near $500 million.
- The article does not provide additional financial or commercial terms.
Pricing and suitability for a robotics lab
The available material does not disclose Mecka AI’s pricing model, minimum commitment, licensing terms or whether access is practical for a mid-sized robotics lab. A useful assessment would require a quote tied to the required tasks, data volume, annotation depth, usage rights and quality controls.
- No public price or standard package is established by the supplied information.
- Suitability depends on the lab’s task definitions, budget and required data rights.
- A paid pilot can test data quality and workflow fit before a larger commitment.
OEM integration and onboarding questions
Nothing in the supplied material shows that Mecka AI is plug and play with robot OEM hardware. Integration effort could depend on data schemas, sensor alignment, model pipelines and validation requirements, but no API, SDK, supported-hardware list or onboarding process is described here.
- Confirm supported file formats, labels, sensors and delivery methods.
- Check how demonstrations map to the target robot’s embodiment and controls.
- Define acceptance criteria, failed-sample handling and dataset versioning.
- Request an onboarding plan rather than assuming immediate hardware compatibility.
Frequently asked questions
Is there enough evidence for a Mecka AI review?
Not yet from the supplied information. It explains the company’s model and financing but provides no independent trial, delivery benchmark or named customer result. A robotics lab should evaluate a representative sample against its own acceptance criteria.
Is Mecka better than Remotasks for egocentric robotics data?
The supplied evidence does not support that conclusion. It does not confirm Mecka AI’s camera perspective or provide comparable information about coverage, quality controls, rights, delivery times or robotics-specific workflows.
How does Mecka compare with Outlier AI for robotics training data?
There is not enough comparable evidence here to rank them or determine which one delivers better results. A fair comparison requires the same task specification, data volume, quality threshold and usage-rights requirements.
What are the potential pros and cons of Mecka for physical AI infrastructure?
The potential benefit is access to human-motion demonstrations tied to real tasks. Open questions include dataset coverage, consistency, rights, integration effort, validation, pricing and support for a lab’s target robot.
Which enterprises use Mecka AI for robot deployment?
The supplied material names investors but no enterprise customers or production robot deployments. Investor participation should not be interpreted as evidence of customer adoption.

