| name | sales-snipcart |
| description | Snipcart platform help — developer-first embeddable shopping cart for static/JAMstack/custom sites (Hugo, Gatsby, Next.js, Astro, WordPress): define products with data-item-* HTML attributes and Snipcart injects the cart/checkout, validating prices by crawling your product URLs. REST API (app.snipcart.com/api, Basic auth with the secret key as username), webhooks with token-callback validation, a JS SDK, and an official hosted MCP Server for Claude/Cursor. Use when checkout fails with product-crawling-failed or a price-mismatch error, cart items won't add because data-item-id/price/name/url attributes are missing, products on a JS-rendered or headless-CMS page can't be validated, verifying webhooks via the X-Snipcart-RequestToken callback, managing orders/discounts through the MCP server or REST API, or weighing the 2% transaction fee against the flat fee at low volume. Do NOT use for cart-platform selection or checkout strategy (use /sales-checkout) or widget-store platforms like Ecwid (use /sales-ecwid). |
| argument-hint | [describe what you need help with in Snipcart] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","checkout","ecommerce","platform"] |
| github | https://github.com/snipcart |
Snipcart Platform Help
Snipcart is a developer-first embeddable cart: a JS snippet plus data-item-* buy-button attributes turn any static/JAMstack/custom site into a store. Its signature mechanic — and #1 error class — is price validation by crawling your product URLs. Automation runs through a REST API, webhooks with token-callback verification, a JS SDK, and an official hosted MCP server.
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
Ask only what you can't infer from the user's prompt:
-
What are you trying to do?
- A) Add Snipcart to a site (which stack — Hugo/Gatsby/Next/Astro/WordPress/custom?)
- B) Fix a checkout/validation error (
product-crawling-failed, price mismatch, missing attributes)
- C) Integrate orders with a CRM/fulfillment/warehouse (API, webhooks, MCP)
- D) Understand pricing (2% vs $20/mo minimum) or Test vs Live modes
- E) Custom shipping/taxes/subscriptions
-
Is the product page server-rendered? JS-rendered pages break the price crawler — the fix differs (JSON crawling endpoint vs SSR).
Skip-ahead rule: if the user's prompt already has enough context, go straight to Step 2.
Step 2 — Route or answer directly
| If the user's question is about… | Route to |
|---|
| Which cart/commerce platform to pick (Snipcart vs Ecwid/Foxy/Shopify Buy Button/Stripe Checkout) | /sales-checkout {question} |
| Widget-store platforms (Ecwid) | /sales-ecwid {question} |
| Checkout-conversion strategy across tools | /sales-checkout {question} |
| Selling digital downloads strategy | /sales-digital-products {question} |
| Tax / Merchant-of-Record obligations | /sales-merchant-of-record {question} |
When routing, give the exact command: "This is a {domain} question — run: /sales-checkout {original question}"
Otherwise, answer Snipcart-specific questions directly using Step 3.
Step 3 — Snipcart platform reference
Read references/platform-guide.md for the full reference — capabilities & automation surface, pricing, data model (products live in your markup), and quick-start recipes (token-validated webhook listener, order pulls, the JSON-crawling-endpoint fix).
