Connect the store where your AI product earns revenue.

What it reads

Store-scoped orders, renewals and customers

• The stores available to the connected account, so you can choose one.
• Paid, partially refunded, and refunded order facts for that store.
• Eligible renewal records from subscription-invoices. Initial subscription invoices are excluded so the initial order is not counted twice; invoices with an unknown billing reason are not assumed to be renewals.
• 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 and eligible renewal invoices 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

Provider refund time is used when available. Otherwise an order's updated_at or original order time is a fallback, not proof of the exact refund event time. The connector reads API snapshots; it does not implement a dedicated merchant refund webhook ledger. Approximate timing and bounded or truncated imports limit contribution decisions. Processor fees remain unavailable. See the shared revenue-basis guide.