> For the complete documentation index, see [llms.txt](https://docs.scraperapi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scraperapi.com/synchronous-apis/overview.md).

# Overview

When you route requests through our Synchronous API `https://api.scraperapi.com` we will return the raw HTML output of the target URL. This method is **simple**, **fast** and works seamlessly with any HTTP client.

### Highlights

* **Quick response** - results are typically returned within seconds, but complex domains can take as long as **60 seconds**.
* **Seamless integration** - works with any HTTP client or library.
* **Workflow friendly** – fits naturally into pipelines or apps where data is consumed in real time.
* **Easy to debug** - test and adjust parameters within seconds.

### Constraints

* 50MB max response size.
* 70-second recommended timeout.

### Costs

* Normal (flat) requests typically cost 1 API credit. Additional costs may apply in some cases, such as when extra parameters are enabled or certain domains are scraped. You can learn more about costs [here](/getting-started/quick-start/credits-and-requests-costs.md).
* **Cost Control** - You can use the `max_cost` parameter to cap how many API Credits a request may consume. If the cost exceeds the specified limit, the API will return a `403 error`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.scraperapi.com/synchronous-apis/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.