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

# Overview

Hyper Solutions is a **payload-generation API** for request-based scraping. It generates the sensor data, cookies, and tokens that anti-bot systems (**Akamai Bot Manager, Incapsula/Imperva, DataDome, and Kasada**) expect from a real browser, so you can access protected sites with plain HTTP requests instead of running a headless browser.

## The mental model

The single most important thing to understand: **the API never talks to the target site.** It does not fetch pages or solve challenges over the network for you.

Instead, **your code** owns all traffic to the target. You collect the inputs a challenge needs (script contents, cookies, UUIDs, your IP, your User-Agent), send those inputs to `*.hypersolutions.co`, and get back the payload a real browser would have produced. You then POST that payload to the target yourself.

<figure><img src="/files/SXaO1l1kspVblXnkiYU6" alt="Your code fetches the page and script from the target site, sends those inputs to the Hyper Solutions API, gets back a generated payload or token, and posts it back to the target to obtain a valid cookie."><figcaption></figcaption></figure>

Because your code owns steps 1 and 5, **the quality of your HTTP client matters as much as the payload.** When a request is blocked even though the generated payload looks correct, the cause is almost always in your request (the TLS fingerprint, header order, cookies, or IP) not in the payload. That is why the [Core Requirements](/start-here/core-requirements.md) page exists and why every integration guide repeats them.

## What you're responsible for

* A **browser-grade TLS client** (standard HTTP libraries are blocked on sight).
* **Exact browser header order**, including HTTP/2 pseudo-headers.
* **Session consistency**: the same User-Agent, TLS fingerprint, IP, and header order for the whole flow.
* **Sticky proxies** whose IP matches what you send to the API.

See [Core Requirements](/start-here/core-requirements.md) for the details.

## What Hyper Solutions handles

| Anti-bot system         | What we generate                                                         |
| ----------------------- | ------------------------------------------------------------------------ |
| **Akamai Bot Manager**  | `_abck` sensor data, SBSD payloads, SEC-CPT (428) proof-of-work, pixel   |
| **Incapsula / Imperva** | `reese84` sensors (static + dynamic), `___utmvc` cookies                 |
| **DataDome**            | interstitial + slider payloads, tags telemetry                           |
| **Kasada**              | challenge tokens, per-request proof-of-work, Vercel BotID (`x-is-human`) |

## Where to go next

1. [**Quickstart**](/start-here/quickstart.md): get an API key and a working SDK in a few minutes.
2. [**Core Requirements**](/start-here/core-requirements.md): the non-negotiables every integration needs.
3. [**Request-Based Basics**](/request-based-basics/tls-fingerprinting.md): the concepts behind TLS fingerprinting and header order.
4. **Pick your anti-bot**: head to the matching guide (Akamai, Incapsula, DataDome, or Kasada) and follow its Getting Started.