Caper
Caper (caper.ai) is a New York-founded computer-vision company that builds AI-powered smart shopping carts and cashierless checkout technology for grocery and retail. Its Caper Cart uses a set of onboard cameras and deep-learning object recognition, running on NVIDIA Jetson edge AI, to auto-detect items as shoppers add them and let customers skip the checkout line. Founded in 2016 (Y Combinator) by Lindon Gao and team, Caper was acquired by Instacart in 2021 for roughly $350M and now operates as part of the Instacart Enterprise Platform (Connected Stores), deployed with retailers including ALDI and Coles. Caper ships retail hardware and an internal edge/vision platform; it does not publish a public developer API, OpenAPI, SDKs, or a developer portal.
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.
Caper is tracked in the API Evangelist network. This page is the human-readable profile that sits on top of the machine-readable index we maintain at apis.io.
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 — Caper scores 7.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.
Resources
Every other property we hold for Caper — 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.
Build 1
SDKs, sample code, and the tooling you integrate with
Company 2
The organization behind the API
Caper is in the network as a tracked entity. We haven't yet indexed a public API surface for it — when one is published, the artifacts, score, and agent-readiness read will appear here automatically. The source repository is where that profile is built.
← All providers · Data indexed from github.com/api-evangelist/caper · machine-readable index on apis.io