Zyte API pricing#
The cost of a Zyte API request depends on the target website and selected features. You get free credit on sign-up to try Zyte API and calculate costs.
Request cost factors#
We aim to make using Zyte API cost-efficient for every request.
Instead of a flat fee per request that may force you to enable Zyte API only for specific requests, we adjust our prices based on how many resources we actually use for any given request. The fewer resources we need to get you a successful response, the less we charge.
To keep our pricing predictable while we do that, we use the following factors to determine the cost of a request:
Website-specific prices may decrease or increase over time, as we find ways to get cheaper access to websites or websites make changes that impact our access costs. However, website-specific prices cannot change more than once a month, and you get a 2-week notice before every website-specific price change.
You can usually perform raw requests at a much lower price than browser-based requests. However, for websites where avoiding bans requires similar resources in both cases, prices can be similar.
There are edge cases of websites where raw requests can be more costly than browser-based requests. This is because, on some websites, raw requests are often used to perform more costly operations than browser-based requests, such as downloading PDF files. Instead of adding an extra pricing variable like network usage or response size, making it harder for you to predict costs, we adjust website-specific prices accordingly.
When using browser-based requests, taking screenshots and using browser actions increases costs.
Browser actions are charged based on their actual CPU and network consumption.
Initial free credit#
After you spend your initial free credit or your first billing month ends, you are not charged anything. Instead, your Zyte API account is suspended. To resume using Zyte API, you first need to enable Zyte API billing by setting a spending limit.
To determine the cost of Zyte API requests for your specific target websites and features, it is best to send test requests, inspect their cost, and extrapolate from that.
You can send test requests any of the following ways:
Use Zyte API client software or an HTTP client, find your request on the Table tab on the Usage Stats page, and click the request ID on the Request ID column to access the Request Summary page for that request.
In the Request Summary page you can see how much 1, 1k, 100k, or 1M identical requests would cost, as well as a cost breakdown that details which features are affecting your request cost, and how much.
You can alternatively open the Usage Stats page, which on the Table tab shows your latest Zyte API requests, and indicates the total cost of each request under the Cost column.
Costs displayed on the Usage Stats page and on the Request Summary page include the volume discount of the billing month when the corresponding request was processed. If you plan on changing your spending limit, and hence your volume discount, you should take that volume discount change into account when calculating costs.
Browser actions are priced based on actual consumption during request processing, so their cost can vary even for the same request. When calculating the cost of requests that use browser actions, sending a few requests to different, typical URLs of a target website is recommended to get a better picture of the average cost of similar requests, and of the cost variability.
You are only charged for successful Zyte API responses.
You are not charged for bad Zyte API responses, such as the ones you get in the following scenarios:
Your request was affected by a download error, temporary or not. Download errors are caused, for example, by ban responses from the target website that Zyte API was not able to avoid.
Your request hit a throttling limit.
Your request was affected by a server-side error, such as system overload, or a server-side timeout.
Your request was invalid, e.g. invalid JSON, invalid parameters, or incompatible parameters.
See Zyte API HTTP API for all possible bad Zyte API responses.
The following scenarios do not cause a bad Zyte API response:
Responses from target websites with HTTP status codes other than 200, unless they are the result of a ban.
For example, if you send a request to https://toscrape.com/not-found, you get a successful Zyte API response, where the value of the
If you ever get a successful Zyte API response wrapping a ban response from the target website, please contact support.
Browser action failures, such as timeouts.
Zyte API returns your requested output (e.g. browser HTML, screenshot) the way it was at the time of the action error, and the Zyte API response includes an
actionskey with details about the outcome of each action.
Your Zyte API spending limit is the maximum amount that you can be charged for Zyte API usage during a billing month. Once you reach your spending limit, Zyte API stops accepting requests from you until your next billing month starts.
You can see your spending limit on the Billing page.
When your initial free credit runs out or expires, your spending limit is unset, and Zyte API stops accepting requests from you. To resume Zyte API usage, set your spending limit. You can also set your spending limit before your initial free credit runs out or expires, to ensure uninterrupted service.
You can change your spending limit at any time. However, if you need to increase your spending limit beyond double the value it had at the beginning of your current billing month, you must contact support.
For example, if you started your current billing month with a spending limit of $50, you can increase it up to $100. To increase it further, you must either contact support or wait until your next billing month, when you can increase it again, this time up to $200.
When you increase your spending limit:
Your spending limit changes immediately.
If you were not able to use Zyte API because you had reached your previous spending limit, you can immediately resume Zyte API usage.
Your Zyte API monthly commitment is an amount that you pay upfront at the beginning of every billing month. When the next billing month starts, if your Zyte API spending was higher than your monthly commitment, you pay the difference.
For example, if your monthly commitment is $25, you pay $25 at the beginning of every billing month. If during a billing month you spend $40, at the start of the next billing month you pay $15 for additional usage from the previous billing month. If during a billing month you spend $20, at the start of the next billing month you do not pay for additional usage, but you do not get $5 back either.
You can set a spending limit of up to $25 without a monthly commitment. For higher spending limits, however, you must agree to a monthly commitment equal to half your spending limit. For example, to set a spending limit of $26, you must agree to a monthly commitment of $13.
Based on your spending limit, we automatically grant you a discount on every Zyte API request: your Zyte API volume discount. The higher your spending limit, the higher your volume discount.
You can use the spending limit slider on the Billing page to find out the volume discount applied for different spending limit values.
You can pay using a credit card or a PayPal account.