| name | sales-foxy |
| description | Foxy (foxy.io) platform help — hosted cart/checkout layer that bolts commerce onto any site or CMS (Webflow, WordPress, Squarespace, Wix, Framer): add-to-cart links/forms on your pages, Foxy hosts the cart, customizable checkout, and receipt; physical/digital/subscription/donation products via 100+ gateways. Automation through the hAPI (hypermedia REST API at api.foxy.io, OAuth 2.0, HATEOAS link relations, official SDKs), HMAC-signed JSON webhooks with documented retries, and HMAC cart-link signing to stop price tampering. Use when securing add-to-cart links/forms so buyers can't edit prices, verifying Foxy-Webhook-Signature payloads, a webhook auto-deactivated after repeated failures, syncing transactions/subscriptions into a CRM via the hAPI, or the cart/checkout looks mismatched with your Webflow site. Do NOT use for cart-platform selection or checkout strategy (use /sales-checkout) or JAMstack markup-defined carts (use /sales-snipcart). |
| argument-hint | [describe what you need help with in Foxy] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","checkout","ecommerce","platform"] |
| github | https://github.com/Foxy |
Foxy Platform Help
Foxy (foxy.io, formerly FoxyCart) is a hosted cart/checkout layer: your site keeps the product pages, Foxy hosts the cart, checkout, and receipt. Products live in add-to-cart links/forms secured by HMAC signing; automation runs through a hypermedia REST API (hAPI, OAuth 2.0) and HMAC-signed webhooks with real retry semantics. The go-to when a Webflow/builder site outgrows native ecommerce.
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 Foxy to a site (Webflow/WordPress/Squarespace/Wix/Framer/custom)
- B) Secure products — HMAC-sign add-to-cart links/forms
- C) Integrate transactions/subscriptions with a CRM/fulfillment (hAPI, webhooks)
- D) Style the cart/checkout to match the site (template sets)
- E) Understand pricing (plan + 1% capped per-transaction fee)
-
Do you have a build step or serverless functions? Link signing needs one (SDK signer at build time, or a deployed signer function).
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/checkout platform to pick (Foxy vs Snipcart/Ecwid/Shopify Buy Button) | /sales-checkout {question} |
| JAMstack carts with crawler validation (Snipcart) | /sales-snipcart {question} |
| Widget-store platforms (Ecwid) | /sales-ecwid {question} |
| Checkout-conversion strategy across tools | /sales-checkout {question} |
| Subscription billing strategy / migrating subscribers | /sales-subscription-billing {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 Foxy-specific questions directly using Step 3.
Step 3 — Foxy platform reference
Read for the full reference — capabilities & automation surface, pricing, data model, and quick-start recipes (HMAC webhook verification, build-time link signing, hAPI transaction pulls).
