# Custom Response Headers

We've added the following headers to our API's response, which reveal valuable information about your request and credit usage:

<table><thead><tr><th width="324">Header</th><th width="531">Description</th></tr></thead><tbody><tr><td>[PREFIX]-Client-Cookies</td><td>Javascript-generated cookies, after the target website is loaded</td></tr><tr><td>[PREFIX]-Scraped-Headers</td><td>The response headers of the scraped URL</td></tr><tr><td>[PREFIX]-Scraped-Resolved-Url</td><td>The final scraped URL (in case of redirects)</td></tr><tr><td>[PREFIX]-Call-Credit-Usage</td><td>The credit usage for the respective request</td></tr><tr><td>[PREFIX]-Current-Credit-Usage</td><td>Your total credit usage, after you make the request</td></tr></tbody></table>

Depending on the API you use, the prefix can be:

* WebScrapingAPI: `WSA`
* Amazon API, SERP API or other ecommerce APIs: `Searchdata`


---

# Agent Instructions: 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 current page URL with the `ask` query parameter:

```
GET https://docs.webscrapingapi.com/readme/custom-response-headers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.