Retail Zipline website screenshot

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.

33.3/100 thin ▬ flat Agent 9/100 agent aware saas Full breakdown ↓
scored 2026-09-02 · rubric v0.18.0
AccessSelf serve
1 APIs 1 MCP Servers
RetailRetail OperationsTask ManagementEmployee CommunicationsStore OperationsWorkforceKnowledge BaseSoftware-as-a-ServiceMCPCompany

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-02 · rubric v0.18.0
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/retail-zipline: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

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 SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Retail Zipline Rate Limits

0 limits

RATE LIMITS

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Retail Zipline Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Retail Zipline Trust Center

SOC 2 Type II, CSA STAR Level 1

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Retail Zipline Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

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)

apis.yml Raw ↑
aid: retail-zipline
name: Retail Zipline
description: 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.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  - scopes
  - rate-limits
  - security
  generated: '2026-09-02'
  method: derived
image: https://getzipline.com/wp-content/uploads/2023/05/zipline-logo.png
url: https://raw.githubusercontent.com/api-evangelist/retail-zipline/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-08-26'
modified: '2026-08-26'
tags:
- Retail
- Retail Operations
- Task Management
- Employee Communications
- Store Operations
- Workforce
- Knowledge Base
- Software-as-a-Service
- MCP
- Company
tags_raw:
- Retail
- Retail Operations
- Task Management
- Employee Communications
- Store Operations
- Workforce
- Knowledge Base
- SaaS
- MCP
- Company
apis:
- aid: retail-zipline-mcp
  name: Zipline MCP Server
  description: '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 Metadata. The endpoint lives in the WordPress REST namespace
    (/wp-json/mcp/), so it exposes the marketing/content surface to MCP clients rather than the Zipline retail operations
    product. Authorization is OAuth 2.1 authorization-code with PKCE (S256) against getzipline.com, using the single scope
    "mcp". The live tool list could not be enumerated anonymously: the resource requires a bearer token and the host additionally
    returns a Cloudflare bot-management interstitial to non-browser clients.'
  humanURL: https://getzipline.com/
  baseURL: https://getzipline.com/wp-json/mcp/mcp-oauth-server
  tags:
  - MCP
  - Agents
  - Content
  properties:
  - type: MCPServer
    url: mcp/retail-zipline-mcp.yml
  - type: Authentication
    url: authentication/retail-zipline-authentication.yml
  - type: OAuthScopes
    url: scopes/retail-zipline-scopes.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://getzipline.com/
- type: Documentation
  url: https://support.retailzipline.com/en/
- type: Support
  url: https://support.retailzipline.com/en/
- type: StatusPage
  url: https://status.retailzipline.com/
- type: Pricing
  url: https://getzipline.com/our-pricing/
- type: TermsOfService
  url: https://getzipline.com/terms-and-conditions/
- type: PrivacyPolicy
  url: https://getzipline.com/privacy-policy/
- type: SignUp
  url: https://getzipline.com/request-demo/
- type: Blog
  url: https://getzipline.com/blog/
- type: DeveloperPortal
  url: https://getzipline.com/platform/integrations/
- type: GitHubOrganization
  url: https://github.com/retailzipline
- type: Security
  url: https://getzipline.com/vulnerability-reporting/
- type: TrustCenter
  url: https://trust.getzipline.com/
- type: Compliance
  url: conformance/retail-zipline-conformance.yml
- type: WellKnown
  url: well-known/retail-zipline-well-known.yml
- type: LLMsTxt
  url: llms/retail-zipline-llms.txt
- type: Conformance
  url: conformance/retail-zipline-conformance.yml
- type: Lifecycle
  url: lifecycle/retail-zipline-lifecycle.yml
- type: Conventions
  url: conventions/retail-zipline-conventions.yml
- type: DomainSecurity
  url: security/retail-zipline-domain-security.yml
- type: VulnerabilityDisclosure
  url: security/retail-zipline-vulnerability-disclosure.yml
- type: Plans
  url: plans/retail-zipline-plans-pricing.yml
- type: RateLimits
  url: rate-limits/retail-zipline-rate-limits.yml
- type: Packages
  url: packages/retail-zipline-packages.yml
x-enrichment:
  date: '2026-08-26'
  status: enriched
  artifacts_added: 16
  pass: local-v1

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/retail-zipline"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/retail-zipline/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/retail-zipline/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.