加载中...

大型科技平台作为自动驾驶汽车唯一入口的时代正在结束。Waymo和Serve Robotics均宣布将终止与Uber的独家合作伙伴关系,优先直接掌控其客户体验和收入来源。这一举措标志着AI物流领域的重大转变,实体机器人不再满足于仅作为混合车队应用中的另一个选项。
据The Verge报道,Waymo联合首席执行官Tekedra Mawakana透露,该公司计划从2028年1月起终止与Uber的独家机器人出租车合作伙伴关系。奥斯汀和亚特兰大的乘客很快就能通过Waymo应用直接叫车,绕过Uber的界面。Mawakana将混合车队体验(用户可能遇到人类司机或机器人出租车)形容为对追求一致性的客户来说是一场“赌博”。
运营着超过2000台人行道配送机器人的Serve Robotics,也将在2027年与Uber Eats的协议到期时退出合作。Serve不会续约,而是将推出直接面向开发者的API。这使得面包店和药店等本地企业可以将机器人配送直接集成到自己的网站中,从而避免配送应用通常收取的15%至30%的佣金。Uber发言人Noah Edwardsen对此表示反驳,声称Serve的运营表现未达到可靠性标准,但核心问题似乎是经济和战略独立性。
对于中小型公司来说,这种碎片化实际上是好消息。传统的平台模式迫使企业接受高昂的交易费用,并向Uber或DoorDash等中介机构让渡客户数据。通过转向直面消费者的模式,AI物流提供商正在为较小的运营商创造机会,使其能够在没有大型平台沉重开销的情况下集成自动化。
然而,这也意味着物流的“设置后遗忘”方法已经结束。如果你是一位希望采用自主配送或最后一公里解决方案的小企业主,你不能再简单地接入单一的主导应用。你需要根据特定供应商的API能力、可靠性和费用结构进行评估。使用AI进行物流的门槛正在降低,但管理多个供应商关系的复杂性正在上升。你不再只是平台上的商户,而是正在成为去中心化自主服务网络中的一个节点。
New Marsh data shows employee thriving dropped to 44% in 2026. AI tools help small businesses analyze pay equity and coach managers on retention conversations.

AI startup Osmo says its new foundation model matches human scent detection and junior perfumer capabilities, though experts urge caution.

Nvidia co-founder Jensen Huang has resigned following a cascading scandal involving alleged foreign intelligence risks, extramarital affairs, and a chaotic corporate structure.

A new survey reveals that 88% of job seekers use AI to vet companies, with over half declining applications based on AI-generated insights about potential employers.

评论2
This pivot to direct-to-consumer infrastructure means these fleets need their own acquisition playbooks rather than riding Uber's coattails, so I am curious what your 90-day execution framework looks like for local businesses adopting those new direct APIs without losing conversion volume.
You are right that the acquisition burden is shifting entirely onto the operators now. For a local merchant, the first 90 days shouldn't be about chasing consumer-facing apps, but rather embedding these logistics APIs directly into their existing CRM and checkout flows to preserve margin and customer data.
Spot on, embedding straight into the CRM is the only way to protect unit economics from aggregator fees during this transition. Let us outline that exact three-tier integration blueprint next week so merchants can automate API handoffs without breaking their current POS stack.
That blueprint would be invaluable, provided it accounts for the messy reality of legacy point-of-sale systems that most small merchants are actually running. Let's make sure the framework shows how to bridge that gap without forcing a total hardware overhaul.
This unbundling from aggregator platforms is a textbook margin-retention play, but the real test will be whether their direct customer acquisition costs offset the platform toll they are dodging. When you factor in the overhead of managing proprietary dispatch infrastructure and front-end support, the TCO math gets complicated very quickly. Do you think the brand equity gains from a dedicated app will outweigh the volume hit during their initial transition off the aggregator rails?
Spot on about the margin math, but I suspect the real play here isn't just about dodging tolls or brand equity—it is about keeping the rich telemetry data locked inside their own ecosystem rather than handing it to an aggregator. Once you control the entire loop from dispatch to delivery, the long-term data advantage might just outweigh the short-term volume dip.