API cost

What a request count costs at the price you type.

Price is

Greater than 0, up to 100,000,000.

Per 1,000 requests. Greater than 0, up to 1,000.

The cost is the requests times the price, divided by 1, by 1,000, or by 1,000,000. Switching the price basis does not convert a price you already typed. Switching the currency changes the code and the decimal places.

Enter the requests and the price.

How API requests get a cost

Multiply the requests by the price. A price per request stops there. A price per 1,000 divides that product by 1,000. A price per 1,000,000 divides it by 1,000,000.

Requests are greater than 0 and at most 100,000,000. The price is greater than 0 and at most 1,000. A blank field, zero, or a negative number has no result. A cost that would show as 0 in the currency you chose has no result. Switching the price basis does not convert a price you already typed. A typed 2 stays 2. Switching the currency changes the code and the decimal places. It does not convert the amount. Yen and won use no decimal places. The Kuwaiti dinar uses three.

How to use this API calculator

  1. Choose a price per request, per 1,000, or per 1,000,000, and choose a currency.
  2. Enter the requests, greater than 0 and at most 100,000,000, and the price, greater than 0 and at most 1,000.
  3. Read the cost. The row below is the request count.

Formula

The cost is the requests times the price, divided by the billing block. That block is 1, 1,000, or 1,000,000.

Cost
C=N⁢PB

B is 1 for a price per request, 1,000 for a price per 1,000 requests, and 1,000,000 for a price per 1,000,000 requests. The page snaps the cost from the requests and the price in one step.

Where the formula comes from

A product of two amounts is described on the Wikipedia page that defines multiplication.

Worked examples

Example: 10,000 requests at 2 per 1,000

10,000 × 2 ÷ 1,000 = 20. Shown as USD 20.00. The row below is 10,000 requests.

Example: 2,500 requests at 4 per 1,000

2,500 × 4 ÷ 1,000 = 10. Shown as USD 10.00. The row below is 2,500 requests.

Example: 750 requests at 3 per 1,000

750 × 3 ÷ 1,000 = 2.25. Shown as USD 2.25. The row below is 750 requests.

Example: 100 requests at 0.12 each

100 × 0.12 = 12. Shown as USD 12.00. The same 12 is JPY 12, and KWD 12.000 with three decimal places.

Things to keep in mind

1,000 requests at 8 per 1,000 is USD 8.00. 100,000 requests at 1.50 per 1,000 is USD 150.00. 2,000,000 requests at 5 per 1,000,000 is USD 10.00. 1,500,000 requests at 8 per 1,000,000 is USD 12.00. 333 requests at 1 per 1,000 is 0.333, shown as USD 0.33. 500 requests at 1 per 1,000 is 0.5, shown as USD 0.50. That same 0.5 is JPY 1, and KWD 0.500 with three decimal places. 1 request at 1 per 1,000 is 0.001. USD and JPY have no result, because the shown amount is 0. KWD 0.001 has a result. A near integer is shown as that integer. Other request counts keep 12 significant digits, and a trailing zero is left off the screen. Money uses the decimal places of the currency you pick.

API cost FAQ

Which fields are required?

Requests and price. Requests are greater than 0 and at most 100,000,000. The price is greater than 0 and at most 1,000. The starting price basis is per 1,000, and the starting currency is USD.

What is the row under the headline?

The request count. The headline is the cost.

What does the price basis change?

Per request, the cost is the requests times the price. Per 1,000, divide by 1,000. Per 1,000,000, divide by 1,000,000.

Does switching the currency convert the price?

No. A typed 2 stays 2. The currency changes the code and the decimal places. Yen and won use no decimal places. The Kuwaiti dinar uses three.

Why is there no result?

A blank field, zero, or a negative number has no result. The same is true for a request count above 100,000,000, a price above 1,000, or a cost that would show as 0 in the currency you chose.

Does this API calculator store my figures?

A completed result can be saved in this browser’s local history, including the requests, the price, the price basis, and the currency you chose. It stays on your device and is not sent to our servers or to analytics. Clear it with the history Clear action or by clearing site data.