Zipline
Zipline is a South San Francisco–headquartered autonomous logistics company operating the world's largest commercial drone delivery network, with more than two million customer deliveries flown across the United States, Rwanda, Ghana, Nigeria, Kenya, Côte d'Ivoire, and Japan. Zipline designs, builds, and operates two end-to-end aircraft platforms: Platform 1 (P1, "Sparrow"), a long-range fixed-wing aircraft that launches from a catapult, parachutes payloads from altitude, and is used primarily for national-scale healthcare logistics — delivering blood products, vaccines, medicines, and lab samples to hospitals and clinics — and Platform 2 (P2), a short-range hybrid VTOL aircraft with an autonomous tethered "droid" delivery vehicle that lowers packages from a hovering aircraft directly to a designated point on the ground, enabling precision quick-commerce delivery from restaurants, retailers, pharmacies, and hospitals. Zipline's customer roster includes Walmart, OhioHealth, Michigan Medicine, Cleveland Clinic, Mayo Clinic Florida, MultiCare, Sweetgreen, GNC, Jet's Pizza, the governments of Rwanda, Ghana, Nigeria, and Kenya, and Japan's Toyota Tsusho, with the P2 platform actively scaling across the Dallas–Fort Worth Metroplex, Pea Ridge (AR), and expanding into Houston and Phoenix in 2026. The company also operates one of the largest civil autonomous aviation stacks in the world — proprietary detect-and-avoid, route planning, weather, fleet operations, and flight-control software — and in 2025 received the first-ever FAA Part 135 BVLOS (beyond-visual-line-of-sight) operational approval permitting drone package delivery without visual observers. Zipline is a privately held company; its revenue model is drone-as-a-service contracts with healthcare systems, retailers, restaurant brands, and governments. There is no public developer API, SDK, OpenAPI/AsyncAPI specification, GitHub organization, status page, changelog, or self-service developer portal — integrations with customer systems (order management, EHR, WMS, dispatch) are delivered as managed enterprise integrations rather than as a public programmable API.
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 Zipline the way a machine reads it — 1 machine-readable artifact, 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 — Zipline scores 11.0/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 Zipline
Each block below is one kind of artifact we hold for Zipline. 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 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 Zipline — 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 1
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
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 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/zipline · machine-readable index on apis.io