# AsyncFetcher

Skrape{it} provides different fetcher implementations. All of the Fetchers behave different and you should pick them depending on your needs.

The `AsyncFetcher` is a none-blocking http client. It will send an HTTP-request (with [given request parameters](/docs/http-client/request-options.md), headers etc.) to a given url and returns a result that consists of the http response status as well as of the response headers and body in a none-blocking fashion by the use of coroutines. Thereby it can be convenient called from a suspend function.

**It is fast, robust and result will look simular to what you would get when surfing a page in your browser with deactivated Javascript.**

Thereby it is the best pick if you want to call websites in parallel or at least from a coroutine scope and if you just don't care about the excecution of a websites Javascript. 

{% hint style="info" %}
if you do not need skrape{it}'s full feature set you can use the AsynFetcher standalone by adding the following dependency to your project.
{% endhint %}

{% tabs %}
{% tab title="Gradle" %}
{% code title="build.gradle.kts" %}

```kotlin
dependencies {
    implementation("it.skrape:skrapeit-asyn-fetcher:1.1.5")
}
```

{% endcode %}
{% endtab %}

{% tab title="Maven" %}
{% code title="pom.xml" %}

```markup
<dependency>
  <groupId>it.skrape</groupId>
  <artifactId>skrapeit-async-fetcher</artifactId>
  <version>1.1.5</version>
</dependency>
```

{% endcode %}
{% endtab %}
{% endtabs %}


---

# 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.skrape.it/docs/http-client/fetchers/asyncfetcher.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.