DEPLOYDatabase

Deployment

Serve Robot at Los Angeles

Level 4 autonomous sidewalk delivery robot for last-mile food delivery via Uber Eats. It is a sidewalk delivery robot designed for physical AI applications. Key specifications include Listing: Public, Nasdaq: SERV, Robots: Sidewalk delivery robots (Uber Eats and other partners), Origin: Spun off from Uber/Postmates, Notable incident: Robot 'Nasir' shattered a Chicago CTA bus shelter (Mar 2026), CEO: Ali Kashani, Co-founder: MJ Burk Chun, Stock: Nasdaq: SERV, Total funding: 47M, Partners: Uber Eats.

Serve Robot by Serve Robotics · Catalog entry · 3 sources · not yet field-verified · Sidewalk delivery

Recent coverage

See all coverage →


Operator: Serve Robotics, its largest market. Gen3 sidewalk robots deliver via Uber Eats (since 2022) and DoorDash (multi-year partnership launched 2025-10-09, LA first). Part of a fleet reported at 812 daily active robots across 44 cities / 14 states as of Q1 2026 earnings (~2M cumulative deliveries). Note: the headline '2,000 robots' figure is fleet built/registered, not daily-active.

Key facts

Operator
Serve Robotics
Platforms
Uber Eats, DoorDash
Robot
Gen3 sidewalk delivery

Exposure

Customer segment
consumer
Scale tier
pilot lt10

Each exposure value carries its own basis marker. Aggregators report a number; this surface preserves the source class so verification depth travels with the value.

Safety record

No incidents on record for Serve Robot at Los Angeles.

Only active incidents are counted. Retracted incidents are excluded from this summary but remain reachable at their canonical URLs.

Trust tier
Catalog entry · 3 sources · not yet field-verifiedhow tiers work →
Last updated
2026-08-21
Status
operational
Operator type
maker operated
Scale at site
2 to 10 units
Site environment
outdoor
Location precision
verified coordinates
First seen
2022-01-01
ID
cd000d5a-b091-43c8-b68c-72e2cf0e5c7e

Timeline

  1. Jan 2022
    First recorded
    Serve Robot first documented operating at Los Angeles.
  2. Aug 2026
    Current status: operational, reviewed
    Latest recorded state. New status transitions append here as the deployment-status recorder produces them.

On the deployment map

Free to use on your site, with a link back to DEPLOY.

Serve Robot operates in Los Angeles. Explore the full verified map:

Robot-delivery corridors

Los Angeles is covered by DEPLOY’s robot-delivery corridor tracking. See the corridor view:

Sources (3)

  1. https://about.doordash.com/en-us/news/doordash-serve-launch-partnership
  2. https://techcrunch.com/2025/10/09/doordash-to-use-serve-robotics-sidewalk-robots-for-deliveries-in-los-angeles/
  3. https://www.stocktitan.net/news/SERV/serve-robotics-announces-first-quarter-2026-results-with-3x-3jokz86uimr4.html
Methodology: Verified · 3 sources (no primary) · last reviewed 2026-08-21

Verification posture

Verified

Low confidence

Review state

Stable

Last reviewed 2026-08-21

Maturity + lifecycle

Maturity stage: commercial

Lifecycle: active

Architectural position

Cohort: sidewalk

Sources by quality tier

2
unclassified
Unclassified source
1
secondary-industry-publication
Industry publication

The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.

Methodology surface for Serve Robot at Los Angeles.

Common questions

What is the Serve Robot deployment at Los Angeles?
Serve Robot, built by Serve Robotics, is recorded as a deployment at Los Angeles on the DEPLOY registry. Serve Robotics operates the deployment directly.
Who operates Serve Robot at Los Angeles?
Serve Robotics, the manufacturer of Serve Robot, operates this deployment directly. This is a maker-deploys-its-own-product arrangement rather than a customer pilot.
When did the Serve Robot deployment at Los Angeles go live?
The deployment is recorded as starting January 1, 2022 on the DEPLOY registry. Earlier activity may exist but is not yet sourced.
Have there been incidents at the Serve Robot deployment at Los Angeles?
No active incidents affecting this deployment are recorded on the DEPLOY registry. Absence of recorded incidents is not a guarantee no incident occurred; DEPLOY records only sourced incidents and suppresses retracted ones.

Deploy Watch

Track this deployment.

We notify you when status changes against primary-source evidence, contract events surface, or a related incident is filed.

Machine-readable surfaces