Beta status & limits

• Web / TypeScript SDK, ESM only. Validate native store integrations separately with explicitly configured Apps and credentials.
• No automatic customer-session refresh or generic track() API. Funnel retry replays an original command; it does not start another purchase.
• Use direct subscription APIs or Funnel action nodes for membership operations. Trigger entry uses source: { type: 'trigger', key } on the current start operation.
• Owners, Admins and Developers with App access and apiKeys:write manage keys and allowed origins in SDK setup. Stripe connections and prices require separate explicit configuration.
• Sandbox acceptance and a deployed test environment do not establish production database or Live billing acceptance.

Connect membership cancel/resume controls to business-action nodes for the corresponding membership group. Billing management uses a billing_portal node. The server pins membership and payer identity, then retries using the original receipt.

Stripe changes use previewUpdate → update → readSubscriptionUpdate with frozen proration and immediate/renewal execution. Funnel change_membership uses the same core. Seats and prepaid quantities use their corresponding change types. Shared subscriptions retain sibling plans and validate common billing conditions. Change an existing main membership rather than creating another ordinary main checkout. Native replacement uses store timing and host purchase instructions.

Related:Funnel integration

npm 0.0.1 beta is published. Use the guide's pinned version; latest remains 0.0.1. Match the SDK to the Indiana deployment. Later changes in the current source reference need a separate build and release. Download ZIPs contain host integration files only.

• Customer and App usage analytics include zero-cost AI events, all token pools and exact reported provider costs.
• The package includes balance grant editing and overage-control protocols. Resumable standalone grants require the matching Indiana runtime and database migrations.
• Funnels support backend offer decisions, wait instructions and separate business and credential expiry. renewFunnelRun rotates a credential for the same customer within the original business lifetime.
• OpenRouter usage integration has a separate /openrouter entry and an optional peer dependency; ordinary backend consumers do not need that provider installed.
• Authentication is unchanged: trusted backends use a Secret Key; browsers use a Customer Token issued by the backend.

Pin @tinkerlandai/indiana-sdk@0.0.1. The actual 0.0.1 npm artifact was inspected on 2026-10-14. Its version history is independent of the old personal package @houzhen888/groove-grow. HTTP and SDK references cover current source; do not assume later entries below exist in the installed artifact.

A source package.json still saying 0.0.1 does not put later changes into the tarball released on 2026-10-13. Check production/test deployments, business sandbox/live, npm and native packages separately. Local examples or installed-package checks do not verify real payments.