Is Serve Robotics publicly traded?

Yes. Serve Robotics is NASDAQ-listed (ticker SERV). Per DEPLOY's framework, public-listing verification depth produces structurally distinct verification posture from privately-held cohort entrants: quarterly audited SEC filings (10-Q + 10-K + 8-K) + audited financial statements + investor-disclosure transparency + earnings call communications + risk-factor + executive-compensation disclosure. Per DEPLOY's verified-vs-claimed framework, the public-listing depth makes Serve's verification posture especially clean; investors get audited financial transparency that privately-held cohort entrants (Starship, Cartken, Ottonomy) do not provide.

Where does Serve Robotics operate?

Per registry source-of-truth + Agent A foundational ingest, Serve operates 3-market commercial active deployments: Los Angeles (primary commercial-active market; restaurant + food delivery integrated with Uber Eats); Dallas-Fort Worth (expansion market; commercial active); Vancouver (international expansion; Canadian commercial active). Per Agent A discipline, current operational scope + per-market deployment scale should be verified against current Serve public filings + Uber Eats partnership disclosure. The 3-market commercial active scope is editorially substantive: Serve operates at multi-market commercial state rather than single-market pilot.

What is the Serve Robotics Uber Eats partnership?

Per registry source-of-truth, the Uber Eats partnership is Serve's canonical commercial customer relationship. The partnership operates restaurant + food delivery sidewalk robot operations integrated into Uber Eats consumer app. End-user customers ordering via Uber Eats receive Serve robot delivery as fulfillment option; restaurant partners integrate with Uber Eats + Serve delivery infrastructure. Per Agent A foundational ingest discipline, specific partnership deployment scale + per-route delivery counts + restaurant integration scope should be verified against current Serve public filings + Uber Eats partnership disclosure rather than aggregator-source propagation.

Who backs Serve Robotics?

SoftBank is the canonical strategic investor anchor per registry source-of-truth. Additional investor relationships verifiable through NASDAQ-listed disclosure depth + SEC filings + public funding round disclosures. Per DEPLOY's framework, SoftBank-backed strategic-investor relationship operates as one verification anchor at the capital-structure layer; combined with NASDAQ public-listing verification depth, Serve operates at the cohort's most editorially substantive verification position across capital + financial + operational layers.

How is Serve Robotics different from Starship Technologies?

Both anchor the cohort's two canonical scaled commercial positions with structurally distinct verification depths. Serve Robotics: NASDAQ-listed (SERV); SoftBank-backed; Uber Eats partnership anchor; 3-market commercial active (LA + DFW + Vancouver); public-filing verification depth. Starship Technologies: privately held; Skype co-founders heritage (Heinla + Friis); multi-customer university + supermarket; 3-country operations (US + UK + Estonia); millions of deliveries cap-flagged; private-company verification depth. Per DEPLOY's framework, the two positions are structurally distinct on verification depth (public vs private) + customer-relationship structure (partnership-anchored vs multi-customer) + geographic anchor (multi-country international vs US + Canada).

Explainers Sidewalk delivery robots

What is Serve Robotics?

Serve Robotics is a publicly-traded sidewalk delivery robot company (NASDAQ: SERV), SoftBank-backed, with Uber Eats partnership as the canonical commercial customer relationship. Commercial active in Los Angeles + Dallas-Fort Worth + Vancouver; per Agent A foundational ingest audit-first against Model sources, current operational scope + delivery scale should be verified against current Serve public filings + Uber Eats partnership disclosure. Per DEPLOY's framework, Serve's public-listing verification depth (NASDAQ SEC filings) is editorially substantive: the financial-disclosure transparency makes verified-vs-claimed especially clean. Cohort position: publicly-traded sidewalk delivery anchor + captive service business model + commercial active state.

NASDAQ SERV

Public listing

Uber Eats

Canonical partnership

3 markets

LA + DFW + Vancouver active

SoftBank

Strategic investor anchor

SEC filings

Verification depth

Mid-2026

Snapshot date

Public-listing verification depth makes verified-vs-claimed especially clean

Per DEPLOY's framework, NASDAQ public-listing verification depth produces structurally distinct verification posture from privately-held cohort entrants. Quarterly audited filings: SEC 10-Q + 10-K + 8-K + audited financial statements + risk factors + executive compensation disclosure. Investor-disclosure transparency: shareholder communications + earnings calls + investor presentations produce ongoing verification surface for capability claims + operational scope + financial state. Third-party-audited financials: revenue + costs + path-to-profitability anchored to audit-firm review depth privately-held cohort entrants do not provide. Per DEPLOY's framework, public-listing verification depth makes Serve's verified-vs-claimed positioning especially clean compared to privately-held cohort entrants like Starship + Cartken + Ottonomy.

What Serve Robotics is

Serve Robotics is a publicly-traded sidewalk delivery robot company (NASDAQ: SERV). SoftBank-backed; Uber Eats partnership as the canonical commercial customer relationship. Commercial active in Los Angeles + Dallas-Fort Worth + Vancouver. Per DEPLOY's framework on sidewalk delivery, Serve anchors the cohort's publicly-traded position alongside Starship Technologies (privately held) as the cohort's two canonical scaled commercial entities.

The company's core strategic position: NASDAQ public-listing financial disclosure depth + Uber Eats partnership as commercial-anchor customer relationship. Per DEPLOY's framework, the public-listing verification depth (SEC quarterly filings) is editorially substantive: the financial-disclosure transparency makes verified-vs-claimed especially clean compared to privately-held cohort entrants. Cohort position: publicly-traded sidewalk delivery anchor + captive service business model + commercial active state.

NASDAQ SERV: public-listing verification depth

Per registry source-of-truth, Serve Robotics is NASDAQ-listed (ticker SERV). The public-listing verification depth produces structurally distinct verification posture from privately-held cohort entrants:

Quarterly audited filings: SEC 10-Q + 10-K + 8-K filings produce regulator-required disclosure depth across financial state + material events + executive compensation + risk factors.
Investor-disclosure transparency: shareholder-required communications + earnings calls + investor presentations produce ongoing verification surface for capability claims + operational scope + financial state.
Audited financial statements: third-party-audited revenue + costs + path-to-profitability disclosures produce verification chain that privately-held cohort entrants do not provide.

Per DEPLOY's framework, the public-listing verification depth is editorially substantive: financial-disclosure transparency makes verified-vs-claimed especially clean for Serve compared to privately-held cohort entrants like Starship + Cartken + Ottonomy.

Uber Eats partnership as commercial anchor

Per registry source-of-truth, the Uber Eats partnership is Serve's canonical commercial customer relationship. The partnership operates restaurant + food delivery sidewalk robot operations integrated into Uber Eats consumer app. Per Agent A foundational ingest discipline + DEPLOY cap-flag-as-trust-signal: specific partnership deployment scale + per-route delivery counts + restaurant integration scope should be verified against current Serve public filings + Uber Eats partnership disclosure rather than aggregator-source propagation.

The Uber Eats partnership structurally distinguishes Serve from cohort peers operating standalone delivery platforms (Starship multi-customer university + supermarket; Cartken multi-customer hardware-sale). Per DEPLOY's framework, partnership-anchored deployment is one operational position in the cohort; standalone-platform-anchored deployment is another.

Commercial active geography

Per registry source-of-truth + Agent A foundational ingest audit-first:

Los Angeles: primary commercial-active market; restaurant + food delivery operations integrated with Uber Eats.
Dallas-Fort Worth: expansion market; commercial active operations.
Vancouver: international expansion; Canadian commercial-active deployment.

Per Agent A foundational ingest discipline, current operational scope + per-market deployment scale + per-route delivery counts should be verified against current Serve public filings + Uber Eats partnership disclosure. The 3-market commercial active scope is editorially substantive: Serve operates at multi-market commercial state rather than single-market pilot.

Verification posture

Applying DEPLOY's verified-vs-claimed framework to Serve Robotics:

Company verified at public-listing depth: NASDAQ SERV + SEC filings + audited financials + investor disclosure transparency.
Uber Eats partnership verified: canonical commercial customer relationship; restaurant + food delivery integration anchored to operational footprint.
Multi-market commercial active: Los Angeles + Dallas-Fort Worth + Vancouver verified through per-market deployment + operational records.
SoftBank-backed verified: strategic-investor relationship anchored to public funding round disclosures.
Specific deployment scale + financial state cap-flagged: per Agent A foundational ingest discipline, specific delivery counts + per-market scope + financial sustainability cap-flagged against current Serve public filings + Uber Eats partnership disclosure.

Serve vs Starship: the cohort's two canonical scaled commercial anchors

Per DEPLOY's sidewalk delivery cohort framework, Serve + Starship anchor the cohort's two canonical scaled commercial positions:

Starship Technologies: privately held; multi-country (US + UK + Estonia); college campus + supermarket deployments; millions of deliveries cap-flagged; founded by Skype co-founders.
Serve Robotics: publicly traded (NASDAQ SERV); 3-market commercial active (LA + DFW + Vancouver); Uber Eats partnership anchor; SoftBank-backed.

Per DEPLOY's framework, the two positions are structurally distinct on verification depth (public vs private) + customer-relationship structure (Uber Eats partnership vs multi-customer university + supermarket) + geographic anchor (multi-country international vs US + Canada). Both anchor the cohort's commercial active state; together they represent the two-tier scaled commercial verification anchor in the category.

Where Serve fits in cohort verification spectrum

Per DEPLOY's framework, the cohort spans verification + operational positions:

Publicly-traded commercial active: Serve Robotics (NASDAQ SERV; quarterly audited filings depth).
Privately-held scaled commercial: Starship Technologies (multi-country millions of deliveries cap-flagged).
Hardware-sale verified anchor: Cartken (Melco ~100-Hauler order).
RaaS-lease commercial: Ottonomy (~$999/mo) + Refraction AI.
Verified-deployment pilots: Delivers AI (CVG ~2,000 deliveries).
Wind-down record: Amazon Scout (Oct 6 2022) + FedEx Roxo (2022) + Tortoise (2023).

Serve's NASDAQ-listed position is one of the most editorially substantive verification anchors in the cohort: public-listing financial disclosure transparency makes verified-vs-claimed especially clean across operational scope + financial sustainability + competitive position layers.

Where to go for context

For broader sidewalk delivery cohort context + cohort enumeration + business-model spectrum, see what is a sidewalk delivery robot. For the canonical scaled commercial sidewalk delivery anchor (privately held), see what is Starship Technologies. For broader physical AI category context, see what is physical AI.

For canonical Serve Robotics institutional depth (founding history + leadership + SEC filings + Uber Eats partnership detail + per-market operational record), see Serve Robotics' registry record. For the framework DEPLOY applies to verifying capability + deployment claims across operators, see how DEPLOY verifies capability claims. For methodology canonical references applicable to Serve Robotics: the 4-way autonomy-boundary taxonomy (operator-supervised L4 sidewalk delivery; Uber Eats partnership scope) + the 9-tier source-quality rubric (Serve SEC + Uber IR source classification).

Source: DEPLOY registry + SEC filings + per-entity operational records + Agent A foundational ingest + Uber Eats partnership disclosure. Verification depth + business model + cohort tier framework.
Entity	Corporate structure	Customer-relationship anchor	Geographic scope
Serve Robotics	NASDAQ-listed (SERV); public-filing depth	Uber Eats partnership	LA + DFW + Vancouver (3 markets)
Starship Technologies	Privately held; cap-flagged at private depth	Multi-customer college campus + supermarket	US + UK + Estonia (3 countries)
Cartken	Privately held; hardware-sale model	Mitsubishi + Uber Eats + Melco ~100-Hauler	Multi-customer hardware-sale
Coco	Privately held	Restaurant partnerships	LA-headquartered
Delivers AI	Privately held	CVG (Cincinnati airport)	Single-venue ~2,000 deliveries verified
Amazon Scout (wind-down comp)	Amazon subsidiary	Discontinued multi-pilot	Discontinued Oct 6 2022

Frequently asked questions

What is Serve Robotics?: Serve Robotics is a publicly-traded sidewalk delivery robot company (NASDAQ: SERV), SoftBank-backed, with Uber Eats partnership as the canonical commercial customer relationship. Commercial active in Los Angeles + Dallas-Fort Worth + Vancouver. Per DEPLOY's sidewalk delivery framework, Serve anchors the cohort's publicly-traded position alongside Starship Technologies (privately held) as the cohort's two canonical scaled commercial entities. Per DEPLOY's framework, public-listing verification depth makes verified-vs-claimed especially clean.
Is Serve Robotics publicly traded?: Yes. Serve Robotics is NASDAQ-listed (ticker SERV). Per DEPLOY's framework, public-listing verification depth produces structurally distinct verification posture from privately-held cohort entrants: quarterly audited SEC filings (10-Q + 10-K + 8-K) + audited financial statements + investor-disclosure transparency + earnings call communications + risk-factor + executive-compensation disclosure. Per DEPLOY's verified-vs-claimed framework, the public-listing depth makes Serve's verification posture especially clean; investors get audited financial transparency that privately-held cohort entrants (Starship, Cartken, Ottonomy) do not provide.
Where does Serve Robotics operate?: Per registry source-of-truth + Agent A foundational ingest, Serve operates 3-market commercial active deployments: Los Angeles (primary commercial-active market; restaurant + food delivery integrated with Uber Eats); Dallas-Fort Worth (expansion market; commercial active); Vancouver (international expansion; Canadian commercial active). Per Agent A discipline, current operational scope + per-market deployment scale should be verified against current Serve public filings + Uber Eats partnership disclosure. The 3-market commercial active scope is editorially substantive: Serve operates at multi-market commercial state rather than single-market pilot.
What is the Serve Robotics Uber Eats partnership?: Per registry source-of-truth, the Uber Eats partnership is Serve's canonical commercial customer relationship. The partnership operates restaurant + food delivery sidewalk robot operations integrated into Uber Eats consumer app. End-user customers ordering via Uber Eats receive Serve robot delivery as fulfillment option; restaurant partners integrate with Uber Eats + Serve delivery infrastructure. Per Agent A foundational ingest discipline, specific partnership deployment scale + per-route delivery counts + restaurant integration scope should be verified against current Serve public filings + Uber Eats partnership disclosure rather than aggregator-source propagation.
Who backs Serve Robotics?: SoftBank is the canonical strategic investor anchor per registry source-of-truth. Additional investor relationships verifiable through NASDAQ-listed disclosure depth + SEC filings + public funding round disclosures. Per DEPLOY's framework, SoftBank-backed strategic-investor relationship operates as one verification anchor at the capital-structure layer; combined with NASDAQ public-listing verification depth, Serve operates at the cohort's most editorially substantive verification position across capital + financial + operational layers.
How is Serve Robotics different from Starship Technologies?: Both anchor the cohort's two canonical scaled commercial positions with structurally distinct verification depths. Serve Robotics: NASDAQ-listed (SERV); SoftBank-backed; Uber Eats partnership anchor; 3-market commercial active (LA + DFW + Vancouver); public-filing verification depth. Starship Technologies: privately held; Skype co-founders heritage (Heinla + Friis); multi-customer university + supermarket; 3-country operations (US + UK + Estonia); millions of deliveries cap-flagged; private-company verification depth. Per DEPLOY's framework, the two positions are structurally distinct on verification depth (public vs private) + customer-relationship structure (partnership-anchored vs multi-customer) + geographic anchor (multi-country international vs US + Canada).

Serve Robotics verified at publicly-traded sidewalk delivery cohort anchor position. NASDAQ-listed (SERV); SoftBank-backed; Uber Eats partnership as canonical commercial customer relationship; commercial active in Los Angeles + Dallas-Fort Worth + Vancouver. Public-listing verification depth (quarterly audited SEC filings + investor disclosure transparency) structurally distinct from privately-held cohort entrants. Cap-flag on specific deployment scale + financial state pending current SEC filings + Uber Eats partnership disclosure. How DEPLOY verifies →

Compare alternatives

Serve Robotics registry entityStarship Technologies explainerCartken registry entityDelivers AI registry entity

Defined terms in this explainer

Deployment

More in sidewalk delivery robots

View all 3 explainers in sidewalk delivery robots →

← All explainers