Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
KWI website screenshot

KWI

KWI is a retail technology company founded in 1985 and headquartered in Melville, New York, that delivers a cloud-based, unified commerce platform for specialty and department retailers. The platform combines an iOS mobile point-of-sale, merchandising and inventory optimization, order management with buy-anywhere / fulfill-from-anywhere fulfillment, CRM, clienteling and loyalty, the Snapshot real-time sales analytics application, and AI product image search, all operated as a SaaS managed service with helpdesk, hardware, and payments support. KWI describes an API layer in its platform architecture used to export data to third-party systems and channels --- CRMs, ERPs, SRPs, and supply chains --- alongside packaged connectors such as Shopify Connect and a Klaviyo connector. As of this profile KWI publishes no public developer portal, API reference, machine-readable specification, or SDKs; integration is delivered through its professional-services organization under customer contract.

human only

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.

Kin Score

API Evangelist profiles KWI 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 — KWI scores 11.9/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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 11.9/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 0.4 / 20
Commercial Clarity 4.7 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile KWI

Each block below is one kind of artifact we hold for KWI. 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.

Kwi Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Every other property we hold for KWI — 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.

Get Started 2

Portal, sign-up, and the first successful call

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Access & Security 1

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 1

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/kwi · machine-readable index on apis.io