Browse documentation

Connect billing to plan limits

Checkout, customer portal routing, webhook storage, and plan-aware word limits stay in sync with your subscription, so upgrades and usage always line up.

REST API v1

Your platform

Overview

View pricing

Start from public plans

Plans define the upgrade story, word limits, API access, and support expectations.

Open billing

Manage workspace billing

Workspace billing connects account state, word balance, and Stripe portal access.

workspace

POST/api/billing/checkout

account scoped

checkout request

POST /api/billing/checkout

1fetch('/api/billing/checkout', {
2  method: 'POST',
3  headers: { 'Content-Type': 'application/json' },
4  body: JSON.stringify({ plan: 'pro', cycle: 'monthly' })
5})

Review board

Checkout

Plan selection posts to the checkout route and limits update with the subscription.

Portal

Signed-in users can be routed to Stripe customer portal after a subscription exists.

Webhooks

Billing events are stored so subscription state can be reconciled with the workspace.

Billing loop

What happens after a user upgrades

Choose a plan

The pricing page determines plan, cycle, word allocation, API access, and checkout copy.

Open checkout

The billing route creates a Stripe Checkout session when live credentials are configured.

Receive webhook

Stripe sends subscription events that can update account plan and word balance.

Manage portal

Subscribed users return to Stripe portal for card, invoice, cancellation, or plan-management flows.

Configuration

Settings the owner confirms before launch

Checkout key

required for checkoutServer-side billing credential for checkout and portal sessions.

Webhook signing key

required for webhooksUsed to verify billing events before updating account state.

Plans

Monthly and annualBoth billing cycles are supported on the same account and workspace.

Site URL

canonical URLUsed for checkout return URLs, sitemap, and production links.

Implementation note. Stripe and Google credentials intentionally remain external configuration. The frontend should communicate the billing flow without hardcoding private secrets.

Next, make it part of your workflow.Continue reading