Costs and control: understand every charge

Identify the billing model

Open the API detail in Catalog. Its pricing table shows whether it charges per request, per token, per request plus tokens, or is free. Some routes have a minimum charge per request. Review it before estimating large volumes.

Use typical cost carefully

The card shows an abbreviated typical call price for comparison. When data is available, this is based on observed usage over the past 30 days. It does not replace the pricing table in the detail. Hover over the price for the exact amount.

Larger files, more tokens, or a minimum charge can change the real price. Run a DEV simulation to validate the contract, then a small Production request to measure your use case.

Know when a call is charged

A live call is charged only for a 2xx response. Validation, authentication, limit, and availability errors do not debit the balance. DEV mode calls are simulations and always cost zero. Free routes also do not charge.

Understand SMS units

For SMS services, price can depend on message units. GSM-7 text fits 160 characters per unit; characters outside that set, including some accents, reduce the limit to 70. Longer messages use more units. Review text and estimated cost before sending.

Check the final amount

1. Open Calls and filter by route, project, or period.
2. Open a detail for status, price, tokens, and execution header.
3. Open Balance and statement to reconcile usage with top-ups.

Projects separate metrics and limits, but all use the same account balance. If a project limit is reached or the balance runs out, the call is rejected before another charge is created.

Quick answers

Next steps