Connect the store where your AI product earns revenue.

What it reads

Store-scoped orders and customers

• The stores available to the connected account, so you can choose one.
• Paid, partially refunded, and refunded order facts for that store.
• Customer identifiers and USD order totals needed for the revenue ledger.
• Pagination and refund-timing coverage needed to decide whether profit is safe to show.

What it does not do

The connector only performs reads

• No creating checkouts, changing subscriptions, or issuing refunds.
• No combining orders from stores you did not select.
• No treating unavailable payment-processor fees as zero.

Lemon Squeezy API keys are not provider-restricted read-only keys. Grow or Die nevertheless uses the connected key only for the documented verification and read requests.

What it unlocks

Observed revenue before unavailable processor fees

Paid and refund-adjusted orders supply revenue and revenue per visitor. When a Lemon customer ID and server-side model usage map to the same product account, the ledger can support customer-level contribution profit.

Current limits

Refund timing and coverage stay explicit

An order snapshot supplies updated_at, not the exact refund event time. Until the dedicated refund webhook ledger exists, Grow or Die marks that timing as approximate and suppresses affected profit decisions. Bounded or truncated order imports also block profit.