Retail Zipline
Retail Zipline, Inc. (branded "Zipline") is a San Francisco-based retail operations software company founded in 2014 by Melissa Wong and Jeremy Baker. Its cloud platform coordinates communications, task management, checklists, audits, learning, knowledge base and performance reporting across headquarters, field leaders and brick-and-mortar store teams, and is used by 130+ global retail brands including Sephora, Lush, Bath & Body Works and Warby Parker. The product is delivered as a multi-tenant Rails application on per-customer subdomains of retailzipline.com, with mobile apps for iOS and Android. Zipline publishes no public OpenAPI, GraphQL schema or developer portal; its integration surface is sold and provisioned through the vendor, while its marketing site publishes an OAuth-protected Model Context Protocol (MCP) endpoint discoverable through RFC 8414 / RFC 9728 well-known metadata.
Retail Zipline publishes 1 API on the APIs.io network. Tagged areas include Retail, Retail Operations, Task Management, Employee Communications, and Store Operations.
Retail Zipline’s developer surface includes documentation, support, pricing, signup flow, engineering blog, and 19 more developer resources.
Kin Score
APIs 1
Individual APIs this provider publishes, each with its own machine-readable definition.
Zipline MCP Server
An OAuth-protected Model Context Protocol (MCP) endpoint published on Zipline's marketing site (getzipline.com), declared by the site's own RFC 9728 OAuth Protected Resource Met...
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
Zipline MCP Server
MCP SERVERPricing Plans 1
Published pricing tiers and plan structures.
Rate Limits 1
Documented rate limits and quota policies.
Retail Zipline Rate Limits
RATE LIMITSSecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes governing access to this provider's APIs.
Resources
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.