EDITORIAL ARTICLE
One-Time Payments and Ongoing Billing: What Is the Difference?
A research agent needs weather data: $0.01 per query or $10 per month. At 100 queries, listed per-use charges total $1; at 2,000, they total $20, so a subscription might be cheaper.
This is arithmetic, not a quote. Check subscription quotas, overages, taxes, network fees and data quality. Billing unit and payment method are different: per-request pricing can be paid by card or stablecoin, while monthly bills can aggregate usage.
Four billing approaches
| Model | How charged | Ask |
|---|---|---|
| Per request | Price per request or item | Are failed calls charged? |
| Subscription | Access or quota per period | Auto-renewal and overages? |
| Usage-based | Meter calls, bytes, tokens or other units and aggregate | How is usage counted and when billed? |
| Ongoing session | Meter under protocol and agreement while service runs | When does it start and stop, and how is cost confirmed? |
Stripe’s invoice documentation describes fixed and metered pricing; vendor calculations, discounts and cycles differ. MPP’s sessions introduction explains one session-payment interaction; protocol support does not imply a universal pricing model.
Setting agent budgets
A one-time query can have a per-purchase and task cap. Ongoing services additionally need cumulative usage, stopping conditions, estimation error and auto-renewal controls. Many concurrent agents can quickly exhaust a budget even when each call is inexpensive.
Reconcile successful calls with charges: a timeout does not necessarily mean the call was free. Use provider status interfaces and contract rules for unknown states.
Include service price, network or processing fees, conversion, minimum spend, taxes and potential retries. The example is illustrative; no real payment or session test was performed.