Waymo
Waymo is the autonomous driving subsidiary of Alphabet, originally spun out of the Google Self-Driving Car Project. The company develops the Waymo Driver, a full Level 4 autonomous driving stack combining custom lidar, radar, and camera sensors with proprietary perception, prediction, and planning models. Waymo One operates a commercial robotaxi service in Phoenix, San Francisco, Los Angeles, Austin, and other expanding US markets, with announced launches in Tokyo and London. The company has logged tens of millions of rider-only miles and reports significantly fewer serious-injury crashes than human-driven benchmarks. Waymo does not publish a traditional public developer API. Its primary developer-facing artifacts are the Waymo Open Dataset, the Waymo Open Motion Dataset, the Waymax JAX-based driving simulator, and a robust research publication catalogue spanning perception, behaviour prediction, planning, simulation, and end-to-end driving. Consumer access is through the Waymo One mobile app.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Waymo the way a machine reads it — 4 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Waymo scores 16.4/100 (emerging), with a separate agent-readiness read of 7/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Waymo
Each block below is one kind of artifact we hold for Waymo. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Waymo Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Waymo Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Waymo Finops
FINOPSSecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Waymo — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 1
Status, limits, changes, and where to get help
Company 7
The organization behind the API
Scroll within the panel for all 7 ·
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/waymo · machine-readable index on apis.io