Zoox
Zoox is an Amazon subsidiary developing a purpose-built, bidirectional, symmetrical robotaxi vehicle designed from the ground up for autonomous ride-hailing rather than retrofitted from a conventional car. The vehicle carries up to four riders in a carriage-style seating layout, has no steering wheel or pedals, and is engineered for dense urban operation. Zoox provides the autonomous driving stack, the vehicle hardware, and a consumer ride-hail app. Commercial robotaxi service has launched in Las Vegas and San Francisco, with expansion announced for Austin, Miami, Atlanta, and Los Angeles. Acquired by Amazon in 2020, Zoox does not publish a public developer API or open research dataset; its public surface is product, ride-experience, and safety content. This profile captures the company surface for API Evangelist reference.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Zoox the way a machine reads it — 2 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 — Zoox scores 11.8/100 (minimal), with a separate agent-readiness read of 0/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 Zoox
Each block below is one kind of artifact we hold for Zoox. 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.
Security Posture 2
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 Zoox — 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.
Access & Security 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 7
The organization behind the API
Scroll within the panel for all 7 ·
Other 5
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/zoox · machine-readable index on apis.io