waymo.com

No evidence that Waymo (waymo.com) is among the 50+ named A2A launch partners (which include Atlassian, Box, Cohere, LangChain, MongoDB, PayPal, Salesforce, SAP, ServiceNow, and Workday) or has subsequently adopted the A2A/Agent2Agent protocol. Waymo is a consumer-facing autonomous vehicle operator with no publicly documented agent interoperability interface of this type. No vendor-specific statements, deprecation notices, or integration announcements relating to A2A were found.

No evidence that Waymo has adopted or been named as a launch/early partner for the Agentic Commerce Protocol (ACP). Confirmed launch partners include retailers such as URBN brands, Coach, Kate Spade, Revolve, Ashley Furniture (via Stripe), and Glossier, Vuori, Spanx, SKIMS (via Shopify) — all consumer retail/e-commerce merchants, not ride-hailing or autonomous vehicle companies. Waymo's commerce surface (ride booking) does not align with the retail checkout focus of ACP's current deployment.

Waymo does not appear among the 60+ named launch partners in AP2's September 2025 announcement or its April 28, 2026 FIDO Alliance donation. Named partners include payment-infrastructure and commerce players such as Mastercard, American Express, PayPal, Adyen, Coinbase, Etsy, Salesforce, and Worldpay — not a ride-hail or autonomous vehicle operator. No Waymo-specific AP2 documentation, mandate endpoint, or partnership statement was found.

No evidence of a Waymo-published MCP server or MCP-compatible endpoint was found across Waymo's official developer surfaces (waymo.com/open, waymo-research GitHub) or broader search. Waymo's publicly documented developer interfaces consist of the Waymo Open Dataset (sensor data download) and Waymax (JAX-based simulator), neither of which exposes an MCP integration. An unofficial, scraping-based ride-price API exists on GitHub (puravparab/waymo-api) but is not Waymo-sanctioned and is unrelated to MCP.

No evidence found that Waymo (waymo.com) participates in MPP as a launch partner, documented adopter, or otherwise. MPP launch-partner evidence points to entities such as MultiversX, xpay, and Formo, with no Waymo presence in any MPP-related announcement or technical documentation. Waymo's public developer and partner surfaces (waymo.com/community/partners) concern autonomous vehicle operations and ride-hail, not machine-to-machine payment settlement infrastructure.

No evidence that Waymo (waymo.com) appears among NLWeb launch partners or adopters. The confirmed early ecosystem participants named in Microsoft's announcement and related coverage include Condé Nast, Redfin, Eventbrite, Priceline, Qdrant, O'Reilly, and Inception — all content/media or developer-tooling vendors, not autonomous-vehicle operators. Waymo's developer surface is focused on ride-hail and fleet APIs, not web-content discovery, making NLWeb adoption structurally unlikely but not actively ruled out by any vendor-specific statement.

Waymo is an autonomous vehicle and ride-hail company with no apparent commercial retail or e-commerce surface; UCP (Universal Commerce Protocol) is designed for retail checkout and product discovery. No evidence found of Waymo implementing or advertising UCP integration — the only commerce-adjacent Waymo partnership found is a delivery pilot with DoorDash (autonomous vehicle deliveries), which is not a UCP merchant/retailer integration. The not_found (rather than confirmed_absent) status reflects the absence of any Waymo-specific statement about UCP — Waymo simply has no obvious use case as a UCP merchant.

No usable finding available for this protocol (no legitimate scan available within the candidate window).

No evidence found linking Waymo or waymo.com to the x402 protocol. Known x402 launch partners and early adopters include Coinbase, Cloudflare, Stellar, and Eco — none of the x402 launch documentation or partner lists reference Waymo. Waymo's public partner pages focus on autonomous vehicle, ride-hail, fleet, and EV-charging integrations with no mention of HTTP-based stablecoin payment infrastructure.

No evidence found of Waymo (waymo.com) having built or published an app on OpenAI's ChatGPT Apps platform using the Apps SDK. Searches surfaced OpenAI's own Apps SDK documentation, Waymo's consumer ride-hailing iOS/Android app, Waymo's open research dataset, and an unofficial third-party Waymo price API on GitHub — none of which indicate a Waymo-built ChatGPT App. No Waymo-OpenAI partnership announcement covering this surface was found.

Research data access interface: provides programmatic access to the Waymo Open Dataset (perception sensor data, motion/interaction scenarios) via a Python library and Google Cloud Storage (gsutil) download mechanism. Covers ML research use cases including object detection, motion forecasting, and sim agent evaluation. Not a ride-booking or fleet-management API; no consumer or partner booking surface is publicly documented.

The Waymo Open Dataset is accessed through a proprietary Python library (waymo-open-dataset) and Google Cloud Storage, both requiring prior registration and license acceptance at waymo.com/open/. A separate research simulator (Waymax) wraps the dataset with a custom RL-compatible API. No publicly documented third-party booking or fleet management API exists; the only confirmed unofficial ride-price API is a community reverse-engineering project explicitly noting Waymo provides no such official interface.

Direct HTTP requests to waymo.com timed out entirely (DNS resolution failed in the sandboxed environment), making it impossible to fetch /llms.txt, /AGENTS.md, /agents.txt, /.well-known/agent, /.well-known/agent-card.json, or /.well-known/ai-plugin.json. Web searches for 'site:waymo.com llms.txt OR agents.txt OR AGENTS.md' returned no Waymo-published results for any of these paths. No third-party references to a self-declaration file at waymo.com were found, but the inability to fetch the domain directly means a not_found determination cannot be made with confidence.