Billing & Pricing

FormShield bills in credits, not raw requests. One credit is the unit of metered usage; every product spends a fixed number of credits per call, and your plan includes a monthly pool of them. Heavier checks cost more credits, so a single shared balance covers every product on one bill.

Plans

Every org starts on Free. Paid plans add a larger monthly credit pool and metered overage; Enterprise is unmetered and sales-led.

Credits per product

Each product spends a fixed number of credits per call. The passive Content Protection beacon is always free, so you can instrument every pageview without touching your balance.

The region and company IP enrichments are included at no extra credit; only rdns (reverse DNS) can add a credit, and only when the hostname isn’t already cached. Every response reports the exact credits charged under metadata (and metadata.enrichment on /v1/ip), so cost is never a surprise.

How metering and overage work

FormShield meters usage per org across the calendar billing period.

• Free hard-stops at 10,000 credits — calls past the limit return 429 QUOTA_EXCEEDED until the period resets. The passive beacon path is never hard-stopped.
• Pro and Business soft-allow past their included credits and bill the overage to a Stripe Billing Meter at the plan’s per-1,000-credit rate. You’re never blocked mid-month for going over.
• Enterprise is unmetered (quota-exempt).

Check your current usage any time:

curl https://api.formshield.dev/v1/orgs/{orgId}/usage \
  -H "Authorization: Bearer fs_live_…"

{
  "plan": "pro",
  "monthly_quota": 50000,
  "used": 18240,
  "remaining": 31760,
  "period": "202606",
  "period_end": "2026-07-01T00:00:00.000Z",
  "overage": 0,
  "subscription_status": "active",
  "trial_end": null
}

When you’re subscribed, period_end is your Stripe billing-period end (not the calendar month). subscription_status is one of active, trialing, past_due, canceled, or incomplete.

The 14-day Pro trial

Upgrading to Pro starts a 14-day free trial that requires a card. Stripe Checkout collects a payment method up front; you’re not charged during the trial, and at day 14 the trial auto-converts to paid Pro unless you cancel first. There’s no automatic drop back to Free — cancel from the billing portal before the trial ends if you don’t want to continue.

While on trial, GET /v1/orgs/{orgId}/usage returns subscription_status: "trialing" and a trial_end ISO timestamp.

Upgrade a plan (Checkout)

Start a subscription from your backend, then redirect the browser to the returned Stripe Checkout URL.

1. Create a checkout session

   POST /v1/orgs/{orgId}/billing/checkout with the target plan. Requires the manage billing capability (org owner or billing role).

   curl -X POST https://api.formshield.dev/v1/orgs/{orgId}/billing/checkout \
     -H "Authorization: Bearer fs_live_…" \
     -H "Content-Type: application/json" \
     -d '{ "plan": "pro" }'

   The plan is pro or business. Optional success_url and cancel_url override where Stripe sends the user afterward.

2. Redirect to Checkout

   The response is { "url": "https://checkout.stripe.com/…", "session_id": "cs_…" }. Send the browser to url. Stripe handles the card and trial; on success the user returns to your success_url.

3. The webhook updates your quota

   FormShield receives the Stripe lifecycle events at POST /webhooks/stripe and updates the org’s plan, quota, and subscription status. The new credits are live within a few minutes.

Manage billing (Portal)

To change a card, view invoices, switch plans, or cancel, open the Stripe Billing Portal.

curl -X POST https://api.formshield.dev/v1/orgs/{orgId}/billing/portal \
  -H "Authorization: Bearer fs_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "return_url": "https://app.formshield.dev/billing" }'

The response is { "url": "https://billing.stripe.com/…" } — redirect the browser there. The portal requires the manage billing capability. Most teams do all of this from the dashboard’s Billing page, which wraps both endpoints.

Common questions

Next steps