What problem does it solve?
Clerk billing setup and subscription-gating is hard to get right because developers must enable billing, configure plans and features in the right Clerk tabs, and then wire rendering and authorization to entitlements.
Core Features & Use Cases
- Render Subscription UI with Clerk Billing Components: Use PricingTable and related patterns to show available plans and open the in-app checkout drawer for upgrades and downgrades.
- Gate Access by Plans and Features: Apply has({ plan }) for tier-level gates and has({ feature }) for capability-level entitlements, including correct B2B org gating with org plans.
- Implement Subscription Lifecycle with Webhooks: Verify and handle Clerk billing webhook events to persist and synchronize subscription status through the subscription lifecycle.
Quick Start
Ask the clerk-billing skill to generate a /pricing route that renders <PricingTable /> and to list the exact dashboard steps needed to enable Billing and create the required user or organization plans before wiring gates like has({ plan }) and has({ feature }).