产品美国

Serve Robotics开放2000台人行道配送机器人,应用和AI智能体可通过API直接调用

发布 阅读约 1 分钟
原文
Serve Robotics开放2000台人行道配送机器人,应用和AI智能体可通过API直接调用 (MEKAWIRE 示意图)

美国人行道配送机器人公司Serve Robotics(纳斯达克代码SERV)于11月11日上线开发者门户,推出公开API和沙盒,开发者、企业和AI智能体可直接询价、调度并追踪其配送机器人。此前其机器人只能通过第三方配送平台使用。

据The Robot Report援引公司公告,真机使用需经公司审批,并受服务区域、时段和货箱尺寸限制;公司称在美国和澳大利亚部署了2000多台机器人。

Serve Robotics于11月11日上线开发者门户,把人行道配送机器人车队向外部软件开放。门户介绍称,Serve配送API用三次调用即可完成询价、派单和追踪,开发者可先在沙盒中开发,再申请抢先体验。The Robot Report援引公司公告称,面向对象包括开发者、企业、爱好者和AI助手,真机使用需经Serve审批。配送限于其服务区域、运营时段和货箱可容纳的物品,派单、路线、导航和远程监管由Serve负责。

从平台供应商转向直销

公司表示,此前其机器人只能通过第三方配送平台使用;目前在美国和澳大利亚部署2000多台,覆盖约300万人和4000多家餐厅,在美国20个城市150多个社区完成数十万单配送。11月5日,Serve还推出Serve Physical AI Services,向其他机器人企业提供车队背后的技术。

MEKAWIRE 分析

Serve试图把租给配送平台的机器人车队变成自己的平台,这几乎是人行道机器人公司赚取高于配送费收入的唯一途径。

按MEKAWIRE计算,每台机器人约对应2家餐厅,用餐高峰之外的闲置时间就是开放API可出售的运力。但门户公开页面和报道均未给出单次价格,且需审批,初期规模不会大。反方观点是渠道冲突:Serve最大的客户是DoorDash等平台。对中国无人配送企业而言,这种向AI智能体开放调度的模式值得关注。后续看API定价、获批开发者数量和下一份季报中的平台收入。

Serve Robotics in 2026: steps MEKAWIRE has covered
  • Jan 20
    Step
    Acquires Diligent Robotics (Moxi hospital robots)
    Channel
    Company
  • Oct 29
    Step
    First market outside the US: Gold Coast, Australia, with DoorDash
    Channel
    Partner platform
  • Nov 5
    Step
    Serve Physical AI Services for other robot builders
    Channel
    Technology licensing
  • Nov 11
    Step
    Public delivery API and sandbox for apps and AI agents
    Channel
    Direct

Nov 5 and Nov 11 entries from Serve's announcements as reported by The Robot Report and the developer portal; earlier entries from MEKAWIRE stories. As of Nov 14, 2026.

这条消息是利好还是利空?

 

要点
上线
2026年11月11日,自动驾驶配送开发者门户
API
询价、派单、追踪三步,并提供沙盒
真机使用
需审批,受服务区域、时段和货箱尺寸限制
车队规模
美澳2000多台(公司数据,据报道)
覆盖
约300万人、4000多家餐厅(公司数据,据报道)
每台对应餐厅
约2家(MEKAWIRE计算)
来源
MEKAWIRE 情报版
  1. 01

    为何重要

    Serve's API lets approved businesses and developers quote, dispatch and track deliveries directly, expanding access beyond third-party delivery platforms. That could create additional demand for its reported fleet of more than 2,000 robots, but the input provides no API adoption, delivery volume or utilization data. Live access remains constrained by approval, geography, operating hours and cargo size.

  2. 02

    竞争对手分析

    The input identifies no competitors or comparable API offerings, so relative pricing, coverage and technical performance cannot be assessed. Serve's concrete change is a direct integration route alongside its existing third-party platform access. Competitive differentiation will depend on service reliability and delivery economics, neither of which is supplied.

  3. 03

    估值背景

    Serve is Nasdaq-listed under SERV, but no share price or market cap is supplied, and its latest valuation is unavailable. The reported $371M total funding is financing raised, not a disclosed valuation. Listed financing events include $100M and $80M registered direct offerings and $86M from December 2024 at-the-market sales and warrant exercises; current cash, cash burn and share dilution are not supplied.

  4. 04

    研究依据

    No research papers are included in the supplied material. The developer portal and company announcement support analysis of product access, but provide no research evidence on autonomy performance or delivery economics.

  5. 05

    供应链影响

    Serve says it builds and operates sidewalk delivery robots, but the input names no component suppliers, manufacturing partners or production capacity. Opening fleet access through an API does not establish additional hardware orders. Fleet availability, maintenance costs and capacity to absorb new demand remain undisclosed.

  6. 06

    后续看点

    Watch for approved live integrations and paid delivery volumes, since sandbox access alone does not establish commercial adoption. Track utilization, revenue per robot and service reliability as evidence of whether the API improves fleet economics. MEKAWIRE's roughly two restaurants per robot is a reach ratio, not a measure of delivery workload.

  7. 07

    分析师观点

    The API creates a plausible route to broader fleet demand, but the supplied facts establish availability rather than commercial traction. Investors should look for incremental paid deliveries and better utilization before assigning value to the developer channel. Reported reach of about 3 million people and more than 4,000 restaurants does not establish active demand.

  8. 08

    值得追问的问题

    How many developers have received live approval, and how many incremental paid deliveries are their integrations generating? What are API pricing, delivery margins and available fleet capacity within approved service areas and hours?