How We Charge You

At Rayobyte, we aim to keep our pricing structure clear and simple. This page explains how we calculate your usage and what counts as a billable request. Understanding how our system processes your API requests will help you optimize your scraping tasks and budget effectively.

---

How We Count Results

When you use our Web Scraping API, results refer to distinct pieces of content (e.g., web page HTML) that the system retrieves from a target website. Each request generates a result, and we classify these results based on HTTP status codes:

• Successful Results (2xx and 4xx)

  • All HTTP responses with a status code in the 2xx (Success) range or the 4xx (Client Error) range are considered successful.

  • Even if the response doesn't contain the information you were hoping to extract, a 2xx or 4xx status code still counts as a successful result because the target website provided a valid response.

    • For example, if you ask us to scrape a page that is a 404, this still required server resources on our side to do the scraping, and therefore, we must charge you accordingly.

• Unsuccessful Results (Anything Else)

  • Responses with HTTP codes outside the 2xx and 4xx ranges (e.g., 5xx server errors) are treated as unsuccessful.

  • You won’t be billed for unsuccessful results caused by system-level issues, such as our API failing to process a request, or if you pass an invalid API Key.

---

Found Incorrect Data? Contact Us!

We strive to provide accurate and reliable scraping, but we know things don’t always go as planned. Some websites occasionally change their anti-scraping detection logic, which might cause our system to return a successful response (2xx or 4xx) even though the page was blocked or the data was incorrect.

If you encounter this issue and believe you shouldn’t be charged, we’re happy to look into it!

Here’s what we need from you:

1. The API request you sent.

2. The output you received from the system.

Send these details to Support, and our team will investigate the issue on our end. If we determine the issue was caused by the target website's changes and not by an error in your configuration, we’ll adjust your billing as appropriate.

💡 Pro Tip: Regularly test your setup on high-priority sites to catch issues early, especially if the site updates frequently.