Serve Robotics has opened a developer portal for apps and AI assistants to request sidewalk-robot deliveries. Developers can begin with simulated deliveries, but a successful sandbox integration does not grant permission to dispatch the company's real fleet.
Serve's formal launch announcement is dated November 11, 2026; the originating Verge report appeared on November 10. The change opens a software route to an existing operated delivery network, previously available through third-party delivery partners. Serve remains responsible for dispatch, routing, navigation and supervision.
Build the delivery lifecycle before requesting live access
The Serve Delivery API guide describes three stages: obtain a quote, create a job from it, and track the job to completion. Its sandbox uses simulated robots and cannot dispatch a real courier. That makes it a place to examine failure handling before a business depends on the service.
The guide gives a concrete timing constraint: a quote expires after five minutes and can be used only once. An app should therefore avoid treating a quote obtained when a customer first opens a cart as a durable commitment for a later checkout. It also documents couriers_busy as an ordinary capacity response, which calls for a deliberate retry, queue or alternative-courier decision.
Moving into production requires a supported service area, a separate production key and account-level fleet access. Partner signup is not yet self-service, according to the guide. The company announcement also limits deliveries to active service areas, operating hours and items that fit the cargo compartment. An open developer portal does not make every address or parcel eligible.
A bounded pilot should test the full handoff
For a merchant, a useful pilot would follow a real order from an approved pickup to an eligible destination, including what staff and customers see if a courier is unavailable. Teams should confirm the current service terms and live access before presenting robot delivery as an available checkout option. The announcement alone does not establish delivery costs or reliability for a particular route.
If an AI assistant can initiate an order, decide which actions it may approve and when a person must confirm. TechKili's report on the Railway–Primcloud agent dispute provides background on defining authority before automated actions; it is a separate case, not evidence of a problem with Serve.
This portal also differs from the Physical AI Services launch on November 5, which offered technology and data services to robotics builders. The new delivery interface is for using Serve's operated fleet. The distinction lets a team evaluate an operated-service integration separately from a project to develop its own robots.
Sources
Related Articles
Gemini 4 Carbon launches with /swarm preview and a warning on quota use
Google's November 10 rollout brings Carbon beyond its earlier defender release. Model access, parallel-agent setup and the cost of finishing a task need separate checks.
Railway–Primcloud agent dispute puts testing permissions under scrutiny
Reported probing and an engineer's acknowledgement raise a scope question for automated testers. Primcloud's terms and OWASP guidance explain where controls belong.
DOJ’s Super Intelligence Task Force consolidates earlier AI enforcement work
The November 5 announcement links to an October 13 memorandum. Its concrete change is an internal merger and coordination remit, with guidance still to follow.
GPT-6-Cyber launches with project approval and API IP restrictions
OpenAI's specialist model adds another option for authorized security research. Permission to call the API and permission to reach a test target remain separate controls.