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

# Overview

What Apex is, how the API fits into your scraper, and the mental model behind every page in these docs.

Protected sites don't trust plain HTTP traffic. Apex is the layer that fixes that: it supplies what the site's checks expect from a browser, so your requests get through.

## How it works

Apex never touches the target site. Your code owns every request; Apex only steps in when a challenge appears.

1. Your client sends the request to the protected page.
2. The site answers with a challenge instead of real content.
3. You send the challenge inputs to the Apex API.
4. Apex returns the payload or token a real browser would have produced.
5. You replay it on your request and get the page.

## What you're responsible for

* A browser-grade TLS client — standard HTTP libraries are flagged immediately.
* 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 Apex.

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

## Supported solvers

Each solver has its own guide with the exact flow, request shape, and gotchas. This list grows over time — check the sidebar for the one that matches your target.

| Anti-bot system     | What you get back                                                                                            |
| ------------------- | ------------------------------------------------------------------------------------------------------------ |
| **Forter**          | sensor payloads, PoW tokens, f\_sdk\_c cookies, forterToken                                                  |
| **Cloudflare JS-D** | cf\_clearance cookies, \_\_cf\_bm cookies                                                                    |
| **CaptchaFox**      | response tokens for the site's backend (siteverify)                                                          |
| **AWS WAF**         | `aws-waf-token` cookies (Challenge) and `aws-waf-captcha-token` cookies (CAPTCHA) to replay on your requests |
| **FriendlyCaptcha** | `frc_tokens` for the site's backend (siteverify)                                                             |
| **Altcha**          | `altcha` payloads for the site's forms (proof-of-work, v1 and v2)                                            |
| **MTCaptcha**       | verified `vt` tokens for the site's forms (image captcha)                                                    |

## Where to go next

1. [**Quickstart**](/start-here/quickstart.md) — make your first authenticated solve.
2. [**Requirements**](/start-here/requirements.md) — the ground rules every integration needs.
3. [**Getting Started**](/start-here/readme.md) — the fast path through these docs.