Your catalog, programmable.

Peak PIM keeps one canonical version of every product, variant, collection, and media file across all your Shopify stores. These pages document the two ways to build on it: a versioned REST API for your systems, and a remote MCP connector for your AI assistants.

API quickstart Connect an AI assistant

REST API · v1

Peak PIM Public API

Read your catalog from any system: cursor-paginated lists, per-store versions, publish state, ETags, and typed errors. Authenticated with scoped API keys.

MCP · remote connector

Peak PIM MCP connector

Give Claude, ChatGPT, or any MCP client safe access to your catalog: browse, compare stores, draft edits, and publish — behind an OAuth consent you control.

Reference

API reference

Every endpoint, parameter, and response shape — plus the machine-readable OpenAPI 3.1 spec at /api/openapi.yaml.

Reference

MCP tool reference

All 12 tools with arguments, required scopes, and behavior notes — from lean product lists to the live Shopify publish tool.

What you can build

Syncs and exports — walk the whole catalog with cursor pagination, then poll updated_since to stay current in your ERP, data warehouse, or storefront.
Multi-store audits — compare an item's canonical values against each store's version to find drift in titles, prices, or SEO fields.
AI catalog operators — let an assistant find every variant missing a SKU, draft the fixes, and publish them to the stores you choose.
Publish monitors — track pending_publish and last_publish_status to alert on failed or forgotten publishes.

How the two surfaces relate

Both speak the same catalog. The REST API is the versioned, supported contract for code — keys, scopes, and stability guarantees. The MCP connector wraps the same data as tools an AI assistant can call, authorized per-connection through an OAuth consent screen with three permission tiers (read / read & write / read, write & publish).

One model to know

Every entity in Peak PIM exists twice: the canonical values every store inherits, and one store version per connected store that can override them. The REST API calls these the entity and its store versions; MCP tool names use the internal words — master for the canonical item, projection for a store version. Same concept everywhere.

For LLMs and agents

This site is written to be machine-readable too. Point your model at /llms.txt for an index, /llms-full.txt for the entire documentation in one plain-text file, or /api/openapi.yaml for the formal API contract.