Welcome to Schematic Docs

Schematic is a usage-based billing engine for AI and software companies. Meter consumption, bill on credits, enforce every limit in real time, and give customers a live view of what they are spending.

Usage-based pricing keeps gaining ground because it lines up what a customer pays with what they actually get out of the product. One of the key risks is when buyers cannot predict the bill. Schematic gives your customers visibility into what they are using, forecasts of where they will land, and spending limits they set themselves, so a usage-based deal clears review at any size of company.

Schematic supports all pricing setups including seats, flat-rate tiers, and hybrid plans. You can price each part of your product the way it actually sells, and change the mix later without touching application code.

Start here

What teams build with Schematic

• Price by usage — meter tokens, agent runs, or whatever unit carries your cost, and turn rising usage into expansion.
• Run credit-based billing — sell a prepaid credit balance that burns down as customers use features.
• Protect your margins — enforce the limits you priced for in real time, before heavy usage erodes a plan.
• Show customers what an action will cost — preview the price before an expensive run, so nobody is surprised by the bill.
• Close custom deals — package bespoke pricing and entitlements for negotiated contracts without touching code.
• Convert and expand users self-serve — let customers sign up, upgrade, and add capacity without talking to sales.

See all 20 use cases >

Where to start

Engineering

• Build with Schematic — the engineering hub, covering the SDKs, the REST API, sample apps, keys, and environments.
• Flags — how an entitlement check resolves at runtime, and what your code gets back.
• Webhooks — subscribe to plan changes and entitlement triggers to drive your own workflows.
• Stripe integration guide — wire Schematic and Stripe together so subscriptions and entitlements stay in step.
• API reference — every REST resource and endpoint, grouped by object.
• MCP server — connect Schematic to Claude and ask about a company’s plan, usage, and overrides in plain language.
• Observability and support — the logs, event history, and debugging tools for a live integration.

Monetization

• Billing models — every way Schematic can charge, and how to pick between them.
• Usage-based billing models — pay as you go, pay in advance, and fixed fee with overage.
• Creating a metered feature — define the event, set the limit per plan, and start reporting usage.
• Credit burndown — sell a credit balance that several features draw down at different rates.

Product and customer ops

• For product teams — the packaging hub, covering plans, add ons, trials, pricing models, and what customers see at checkout.
• Concepts — the vocabulary the rest of the docs assume, including plans, features, entitlements, and credits.
• Reprice and repackage safely — roll out new pricing and migrate existing customers on your terms.
• Company overrides — change one entitlement for one company without touching the plan everyone else is on.
• Handling customer exceptions and feature trials — when to reach for an override, a custom plan, or a time-boxed feature trial.

Finance

• Stripe integration — what Schematic syncs into Stripe, what it reads back, and how the two-way sync behaves.
• Stripe integration guide — how plans, add ons, and metered features line up with Stripe products and prices.
• Collecting tax — Stripe Tax and third-party providers, and what checkout collects from the customer.
• Billing entities — let a parent company pay for another company’s subscription while each keeps its own entitlements.
• Backfills and usage corrections — import historical usage or correct late events so invoices reconcile.
• Troubleshooting — the common broken states, starting with billing and Stripe sync, and how to fix each one.

Community

Join the Schematic Slack community to ask questions and talk to us directly.