> 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/resources/release-notes/october-2026/akamai-protected-sites-now-unblocked-automatically.md).

# Akamai-protected sites now unblocked automatically

You no longer need to add extra parameters to enable Akamai bypass

ScraperAPI now unblocks Akamai-protected sites out of the box. You no longer need to add extra parameters to enable Akamai bypass—simply send your requests as you would for any other site, and ScraperAPI handles the protection automatically.

**What changes for your requests**

A standard request is all you need to get started with an Akamai-protected domain:

```bash
curl "https://api.scraperapi.com/?api_key=YOUR_API_KEY&url=https%3A%2F%2Fexample-akamai-site.com"
```

Replace the example URL with your target URL and use your API key. No Akamai-specific configuration is required, making it easier to add these domains to your existing scraping workflows.

:flashlight: If you currently use `premium=true` or `ultra_premium=true` specifically to access Akamai-protected sites, test your target URLs without those parameters. You no longer need them to activate Akamai bypass, although they may still serve other requirements in your workflow.

#### **Credit cost**

**Check costs before running at scale**

You can confirm the cost of your target URLs and monitor usage through:

* **Domain Multiplier:** Look up a URL’s credit cost directly in your [dashboard](https://dashboard.scraperapi.com/home/domain-multiplier).
* **API Playground:** [Test your target URLs](https://dashboard.scraperapi.com/apiplayground) to verify results and understand credit usage before starting a larger job.
* **Cost API:** Use the `/account/urlcost` endpoint to check costs programmatically. It supports ScraperAPI request parameters so you can check the cost of your intended configuration.
* **Response headers:** Read the `sa-credit-cost` header to see the credit cost of each request.

Domains can change their protection measures over time, and optional request parameters can affect credit usage. Check your target URLs with the settings you plan to use before scaling up.

For more details, see our [credits and request costs documentation](https://docs.scraperapi.com/getting-started/quick-start/credits-and-requests-costs).

<a href="https://docs.scraperapi.com/getting-started/quick-start/credits-and-requests-costs" class="button primary" data-icon="hand-point-right">VISIT DOCS</a><a href="https://dashboard.scraperapi.com/home/domain-multiplier" class="button secondary" data-icon="magnifying-glass">DOMAIN COST ESTIMATOR</a>


---

# 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 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/resources/release-notes/october-2026/akamai-protected-sites-now-unblocked-automatically.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 `automate deployments from our CI pipeline` 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.
