A mechanic and a race engineer on board.
MotoCore One logs everything your engine does, and the AI suite turns that log into answers. Day to day it's a mechanic on board, keeping an eye on your car and flagging things early. On track it's a race engineer, reviewing sessions line by line and debriefing after a session. Grounded in your own telemetry, never generic advice.
Ask the car. Get an engineer's answer.
On the unit or in the web app, ask a question and Claude answers with your car's actual state in front of it: live readings, your engine profile, and a logged session when you point it at one. No appointment, and no waiting-room magazines from 2009.
- Grounded answers. The reply cites the readings it used, so you can check its working.
- Session-aware. Attach a logged session and the answer is drawn from that drive's data.
- Spoken aloud. Answers come through the built-in speaker, so your eyes stay on the road.
- Everywhere you are. The same chat on the device and in the cloud portal.
An OBD2 fault-code reader, built in.
MotoCore One is becoming a full OBD2 fault-code reader. When your engine management light comes on, it reads the stored trouble code (DTC) behind it, explains in plain English what the code means against your own live data, and clears the light once you have fixed the cause. The read a garage charges a diagnostic fee for, on the screen already on your dash. This lands before the public release.
The conversation after the session.
Pick a session and get the debrief a race engineer would give: what the engine did, where the data says the time went, and what to watch next time out.
- Reads the whole log. The session's channels are chunked and fed to Claude, not summarised away.
- Plain-language findings. Trims drifting lean, temperatures creeping, mixture under load.
- Datalog review on tap. The same pipeline reviews any uploaded log, channel by channel.
The full suite. One engineer.
Every capability below runs on the same principle: Claude, grounded in the data MotoCore One actually logged from your car. Think of it as the only mechanic who never sighs when you try to describe the noise it's making.
Ask MotoCore
A question box on the device and in the web portal. Ask about behaviour, maintenance, tuning theory, or “what just happened”, and it answers against your car's data.
AI datalog review
Queue any logged session for review and get a written report back: every channel examined, anomalies called out, verdicts you can act on.
Race-engineer debrief
A structured post-session review in the voice of the pit wall. Findings first, caveats included, no drama.
Vision diagnosis
Photograph what you can see, whether that's a weep under the expansion tank, a perished hose or a connector you cannot place, and ask. Claude reads the image alongside your car's profile.
Co-Pilot voice + wake word
Say the wake word and ask, hands on the wheel. Speech-to-text runs offline on the unit; the answer comes back through the built-in speaker.
Natural-language data query
Ask the log a question in plain English. “Hottest coolant this month”, or “how many pulls over 400 horsepower”, and the answer comes from your own history.
Cloud intelligence, clearly metered.
The AI suite runs on Anthropic Claude in the MotoCore cloud, so it needs a WiFi connection and it uses credits. Everything else on the unit works without either.
- Needs WiFi. Answers come from the cloud; the gauges, navigation, dashcam and timers never do.
- Uses credits. Metered from what a question actually costs to answer, not a flat fee per tap. Every answer shows what it used.
- Included monthly. Every cloud tier carries AI credits: 2 a month on Free, 20 on Standard, 100 on Pro. Top-up packs available.
- Requires a licence. The AI suite is part of the MotoCore cloud account, and the unit stays fully useful without one.
Your data. Your engineer.
Powered by Anthropic Claude, grounded in the telemetry your car actually produced.