Canary for NCR Counterpoint
Partner vault for NCR Counterpoint VARs. The co-sell resource for adding Canary's analytics and agent layer on top of the Counterpoint platform your customers already run.
What Canary is
Canary is an agent-native store operating system that runs above NCR Counterpoint. Two surfaces: an analytics spine (13 ARTS modules that turn Counterpoint data into operational intelligence) and ALX/VSM (the store agent — the MCP endpoint that connects customer Claudes to the store in real time).
Counterpoint is the transaction engine. Canary is what makes it intelligent.
The agent model
Canary runs a hub-and-spoke agent network. Every store gets an ALX (Virtual Store Manager) — the store's MCP endpoint. A back office hub connects all store agents and monitors cross-store LP, transfers, OTB, and device health via Module A. The hub scales to corporate level regardless of org structure.
→ Agent network — how it works
Site sections
| Section | For |
|---|---|
| Deployment Guide | Start here — Frame, People, Agents, Model, and Blueprint for all 6 Phase 1 modules |
| Agent Network | The VSM architecture, hub-and-spoke model, MCP stack, roadmap |
| Verticals | Vertical playbooks — L&G full, Armstrong proof case, others in development |
| Modules | L1–L4 process decomposition of the 13-module Canary Retail Spine |
| Why Canary | Positioning, market context, co-sell story |
| Modernization | The five-phase Counterpoint modernization path — observer to spine to platform |
| NCR Context | NCR platform analysis — why they can't build Layer 4 |
| Integration | Counterpoint API surface and connection model |
| Specs | Architecture and integration depth — master SDD, endpoint catalog, document model, OpenAPI spec |
| Sandbox | Path to demo |
| Pitch | Leave-behinds |
Verticals covered
- Lawn & Garden — lead vertical; full playbook + Armstrong proof case
- Feed & Tack, Gun & Sporting, Beverage, Wine & Spirits — in development