API Billing Terms Template and Drafting Guide
Draft clear API billing terms covering meters, billing periods, overage, credits, taxes, disputes, and service suspension.
Billing terms should explain the meter
API billing terms describe what customers pay for and how the amount is measured. Name each billable unit, state whether usage is rounded, and explain the treatment of failed requests, retries, cached responses, test traffic, and provider errors. Link the legal language to the public pricing documentation instead of maintaining conflicting formulas.
This guide is an operational drafting aid, not legal advice. Have qualified counsel adapt the final terms to your company, jurisdiction, tax treatment, payment provider, and customer type.
Define the billing period and price source
State when the billing period starts and ends, which timezone applies, and whether usage is prepaid, billed in arrears, or deducted from credits. Identify where current rates are published and how much notice customers receive before future price changes.
If a plan includes usage, define the included amount and whether unused units expire, roll over, or remain available after cancellation. For tiered pricing, include a worked example so the customer can distinguish graduated and volume calculations.
| Term | Question to answer | Example approach |
|---|---|---|
| Meter | What activity creates a charge? | Successful output tokens |
| Period | When does usage reset? | Calendar month in UTC |
| Rounding | At what level is usage rounded? | Aggregate exact usage, round invoice total |
| Overage | What happens above included usage? | Hard stop or published per-unit rate |
Cover payment, credits, and overage
Explain accepted payment methods, authorization to charge, invoice timing, payment due dates, taxes, and consequences of failed payment. If customers prepay, state whether credits have cash value, can be transferred, expire, or are refundable.
Overage language should match the product controls. If service continues beyond the included quota, state the applicable rate and make estimated charges visible during the billing period. If the product stops instead, explain the reset and upgrade path.
- Identify the account owner responsible for charges made by all keys in the workspace.
- Require customers to protect credentials and report suspected compromise promptly.
- Describe tax handling and whether displayed prices include applicable taxes.
- State when access may be limited after failed or disputed payment.
Create a fair usage-dispute process
Set a reasonable period for reporting a suspected billing error and list the evidence the customer should provide. Preserve meter records, key identifiers, timestamps, routes, and price versions so the support team can reproduce a charge without exposing sensitive request content.
Distinguish a metering error from valid usage caused by a customer bug or leaked key. The refund policy may allow discretionary credits, but the billing terms should not promise automatic reimbursement for every credential incident.
Use a compact starter structure
A practical document can follow this order: service plans and meters; billing period and calculation; payment authorization; included usage and overage; prepaid credits; taxes; refunds and disputes; customer responsibility for keys; suspension; price changes; and contact information.
Generate an initial draft with the API Key Policy Generator, then compare every sentence with the actual calculator, dashboard, invoice, and enforcement code. The policy is trustworthy only when the product behaves the same way.