What problem does it solve? Adding subscriptions to a Next.js app with Clerk requires coordinating dashboard configuration, plan and feature setup, checkout UI, entitlement checks, and webhook handling, and mistakes in any step cause silent failures like empty pricing tables or false plan checks. ## Core Features & Use Cases - Subscription UI: Render Clerk's PricingTable and in-app checkout drawer, plus UserProfile or OrganizationProfile for billing management, invoices, and payment methods. - Plan and Feature Gating: Gate routes and UI with has({ plan }) for tier-level checks and has({ feature }) for capability-level entitlements, on both server and client. - B2B and B2C Patterns: Configure user plans for B2C and organization plans with seat limits for B2B, including admin-gated billing UI. - Billing Webhooks: Handle the full Clerk event catalog (subscription.created, subscriptionItem.canceled, subscriptionItem.pastDue, and more) to sync subscription state to your database. - Use Case: A SaaS team adds a /pricing page rendering PricingTable, gates the analytics dashboard behind has({ feature: 'analytics' }), and syncs subscription status via verified webhooks. ## Quick Start Ask the AI to add a Clerk billing pricing page to your Next.js app and gate a pro-only route using has({ plan: 'pro' }).
