100 is the example result. Read it using the units and relationship stated below.
API Cost uses requests, cost per request, additional billable units.
Keeping usage and formats tied to the receiving system
For api cost, the relationship is Result = [Requests] × [Cost per request] + [Additional billable units] × [Cost per additional unit]. The amount depends on the supplied requests, cost per request, rather than a live market price or a value imported from another record. A technical estimate needs the billable unit or output format the receiving system expects. Requests, tokens, storage and transfer can have separate rates. A text transformation should preserve meaningful characters rather than promise validation it does not perform.
What the model includes
Result = [Requests] × [Cost per request] + [Additional billable units] × [Cost per additional unit] Use current rate-card values for cost fields and a representative source sample for conversion tools. Cached requests, retries and region charges may change an invoice. A successful local transformation does not establish that an external API will accept the record. Keep the original source alongside the result. Before deployment, check the output in the target environment and record any exclusions, such as a rough token estimate or formatting without a parser.
Example with the supplied inputs
Requests: 100000; Cost per request: 0.001; Additional billable units: 0; Cost per additional unit: 0. Result: 100. The values are illustrative.
Compare one changed input
Requests changes from 100000 to 110000. The result becomes 110. All other inputs remain fixed.
Calculation rule
Result = [Requests] × [Cost per request] + [Additional billable units] × [Cost per additional unit]
Inputs and output
| Input | Example value | Entry convention |
|---|---|---|
| Requests | 100000 | Use the source quantity represented by requests. Keep the counted population fixed and avoid mixing a unit value with a period total. |
| Cost per request | 0.001 | Use cost per request on the currency and period basis shown by the formula. Keep gross amounts, net amounts and unit amounts distinct; the page does not fetch a price or exchange rate. |
| Additional billable units | 0 | Use the source quantity represented by additional billable units. Keep the counted population fixed and avoid mixing a unit value with a period total. |
| Cost per additional unit | 0 | Use cost per additional unit on the currency and period basis shown by the formula. Keep gross amounts, net amounts and unit amounts distinct; the page does not fetch a price or exchange rate. |
Output: 100 is the example result. Read it using the units and relationship stated below. Use the formula to distinguish a cash amount, count, percentage or ratio.
How to use the page
Collect the inputs
Gather Requests, Cost per request, Additional billable units. Use one period and the units shown in the form.
Run the calculation
Enter the values and select the action. The calculation rule above explains how the inputs produce the result.
Compare a scenario
Change Requests on its own, keeping the other inputs fixed. Read both results before changing another assumption.
Worked example
With the example inputs listed above, the result is 100.
Change Requests from 100000 to 110000 while keeping every other value fixed. The result becomes 110. This comparison isolates that input; it does not forecast how other variables will respond.
Check the stated formula, units and limits before using the result in a decision.
Keep the displayed formula, input units and model scope with the result. Corrections or questions can be sent through the request section on this page.
Content updated: October 11, 2026