What problem does it solve? Adding subscription monetization to a Next.js app with Clerk auth requires coordinating dashboard configuration, plan and feature setup, entitlement checks, and webhook handling, with many non-obvious pitfalls like wrong plan tabs, stale session tokens, and Stripe-vs-Clerk event name confusion. ## Core Features & Use Cases - Pricing and Checkout UI: Render <PricingTable /> and <CheckoutButton /> to display plans and open Clerk's in-app checkout drawer for B2C users or B2B organizations. - Plan and Feature Gating: Gate routes, API endpoints, and UI elements with has({ plan }) and has({ feature }) from auth() or useAuth(), including seat-limit org plans for B2B. - Billing Webhooks: Handle the full Clerk billing event catalog (subscription.created, subscriptionItem.canceled, subscriptionItem.pastDue, etc.) with verifyWebhook to sync subscription state to your database. - Use Case: A SaaS team adds a pricing page, gates an analytics dashboard behind the pro plan, enforces a 10-seat cap on the org team plan, and syncs cancellations to their database via webhooks. ## Quick Start Ask the AI to add a Clerk Billing pricing page with plan gating to your Next.js app, and it will enable billing, render the PricingTable, and protect your routes.