How it works
How robotaxi fleet operations work
A mess becomes a clean car without you touching anything. Five steps, designed to run without you once your rules are set. The loop runs today against Tesla’s fleet API in a test environment with simulated vehicles; it has not yet run against a customer fleet, because none exists yet.
01
Detection
Telemetry from the vehicle resolves into one queue of things wrong with the fleet. Tire pressure, charge level, location and vehicle alerts come from the fleet API; interior condition comes from rider reports and inspections today, and from cabin sensing where a vehicle exposes it. Everything lands in the same place, scored by how much earning time it is costing you.
02
Withdrawal from the network
A car that is not fit to carry a rider stops being offered one. mersul marks it unavailable before the next dispatch rather than after a complaint, and the clock on the incident starts there.
03
Ranking and dispatch
Local vendors are scored on distance, ETA against their own history, reliability index and price. The winner gets a ping with the scope and the payout already set and thirty seconds to accept. Your preferred vendors are ranked first, and anything over your approval ceiling comes to your phone instead.
04
Job-scoped vehicle access
The accepted vendor is granted access to one car, for one job, live only while their phone is at the vehicle, and withdrawn the moment the work verifies. Every command is logged against the person who issued it.
05
Verification and return to service
Before-and-after photos are graded automatically against the scope that was dispatched. A pass releases the car back onto the network and releases the vendor’s payment; a fail sends the job back with the reason attached.
What it runs on
Fleet telemetry in, dispatched work out.
What mersul reads
Location, state of charge, tire pressure, vehicle alerts and API connection health, over the fleet API you authorize on Tesla’s own page. Interior condition is not among the fields Tesla publishes, so we take it from rider reports, vendor inspections and any cabin sensing the vehicle exposes.
What it never reads
Your Tesla password. Authorization happens on Tesla’s page and returns a token, which you can revoke from your Tesla account at any time.
What you set once
Your approval ceiling, which vendor tiers each kind of work may go to, your preferred bench in order, and whether the open marketplace is allowed to step in.
When it does not go to plan
The exceptions are the product.
Automation you cannot predict is automation you will not leave running overnight. These are the four ways a job goes sideways and what happens in each.
- Nobody accepts
- The dispatch widens through your bench, then to the open marketplace if you allow it, then escalates to you with the ranked options rather than sitting silently.
- The quote comes in high
- Anything above your ceiling arrives as a push notification with the estimate and photos, and approve, decline and rebid on the notification itself.
- The photos fail
- The job reopens with the failing check named. Repeated first-time failures pull the vendor’s reliability index down, which is what governs whether they see your work again.
- The car cannot be reached
- A stranded or unresponsive vehicle escalates on a ladder — notification, SMS, then voice — instead of waiting for the next telemetry poll.
The marketplace
Your city already has the people. It has no way to reach your car.
Mobile detailers, express washes, mobile tire, Tesla-trained mechanics, biohazard specialists — they are all already working, and none of them can bid on a job that a car reports itself. We rank them for you on distance, ETA, reliability and price, then grant the winner access scoped to that car and that job.
You keep the say. Rank your favorites first, block anyone you refuse to work with, and decide whether the open marketplace is allowed to step in when your picks are busy. Different messes can route to different vendors — a crumb job and a biohazard are not the same call.