lettuce.bot is our design for dispatching a humanoid, a vehicle, or a ground unit to do the physical work — the errands, the upkeep, the labor you'd rather not spend your Saturday on. One request, matched to whichever machine is built for it.
Built on the same account and infrastructure as the rest of the Lettuce network. Nothing on this page dispatches a real machine yet.
Every request gets routed to the form factor built for it. None of this is running yet — this is the architecture we're designing toward.
Hands-and-feet labor inside the walls of a home or a business — where dexterity matters more than horsepower.
Autonomous driving for anything that has to move — across the neighborhood or across town, unattended.
Low, wheeled, weatherproof machines built for the outdoors — property lines, not living rooms.
A first slice of the work we're designing around — the request schema is deliberately generic, so this list only grows.
Hand off the list. A vehicle unit makes the trip, checks it off, and brings it to the door.
Recurring or one-off — dishes, surfaces, laundry — a humanoid unit works while you're out or in.
Mowing, edging, seasonal clearing from a ground unit that already knows your property lines.
Boxes, furniture, the couch that needs two people — a humanoid unit brings the second pair of hands.
Feeding, walks, and a check-in — scheduled around your day, not a stranger's.
Gutters cleared, patio stowed, walkways salted — before the weather makes it worse.
Dry cleaning, prescriptions, the package that has to go back — a vehicle unit runs it down.
Set up before, clean up after — chairs, tables, and the mess a party leaves behind.
The task field is open-ended by design — new categories arrive without a new endpoint.
The plan: describe the job in plain language, we match it to the right kind of unit, you watch it happen, you pay once it's done.
"Mow the backyard Thursday" or "pick up the grocery order at five." Plain language, no forms to fill out.
The request routes to whichever fleet fits — humanoid, vehicle, or ground unit — based on the task and where you are.
Status from dispatch to completion, the same way you'd track anything else moving toward you today.
One quote before the job starts, one charge when it's finished — no surprise line items after the fact.
This is the request shape we're designing /api/bot/tasks around — a task and a location in, a matched unit and a quote back. Nothing here is wired up to hardware yet.
// request { "task": "grocery-run", "details": "Weekly order from the usual list", "location": { "lat": 37.76, "lng": -122.42 }, "window": { "start": "2026-09-11T17:00:00Z" } } // response (draft — not live) { "taskId": "bot_8f3ke2", "status": "pending_launch", "matched": { "fleet": "vehicle", "eta": "tbd" }, "quote": { "currency": "usd", "amount": null }, "note": "lettuce.bot is in development — this call is not live yet" }
We're building lettuce.bot in the open. Every row here is still in design — join the waitlist and we'll email you as pieces of this actually ship.
One email when lettuce.bot opens for early access. No spam, no marketing lists.
No. This page describes the design we're building toward — a way to request a humanoid, vehicle, or ground unit for real-world work. Nothing on this page dispatches a real machine yet.
Grocery runs, deep cleaning, lawn care, moving help, pet care, and general errands — chosen because they map cleanly onto our three planned fleet types, with room to grow well past them.
Each job suits a different form factor. Humanoids handle dexterous work indoors, vehicles handle anything that needs to move across distance, and ground units handle outdoor yard and perimeter work. One request API routes to whichever fits.
That's the plan — one Lettuce account across the network, the same way lettuce.rsvp and the rest of the ecosystem work today.
Join the waitlist above. We'll only email when there's something real to try.
lettuce