Most video AI pilots die the same death. And after trying Perceptron Mk1, I think I understand why.
The model output usually stops at "here's what happened." Interesting for a demo, but difficult to operationalize. Teams struggle to query it reliably, clip from it, or connect it into downstream systems.
What stood out to me with Perceptron Mk1 was the structure of the output itself.
I tested the robotics workflow with timestamped actions, segmented subgoals, and clean structured responses that can plug directly into a pipeline. Timecodes, clips, points, and boxes came back natively as part of the output itself.
That changes the experience completely. It feels less like a capability demo and more like infrastructure teams can actually build on.
EgoSchema: 80.60%. Perception Test: 80.8%, and priced below Flash Lite.
The benchmarks are strong. The structured output is what makes them matter.
The naming is smart too. “Mk1” immediately feels like a flagship system built for the physical world. Simple enough to reference in conversation, distinct enough to become its own model category over time.
Video
Perceptron AI (@perceptroninc)
Today we're releasing Perceptron Mk1: frontier video and embodied reasoning.
Video
— https://nitter.net/perceptroninc/status/2054216828285796630#m