> For the complete documentation index, see [llms.txt](https://docs.vsat.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vsat.dev/reference/tips.md).

# Integration tips

The solver produces a payload for one browser identity. Your job is to make every request in the flow look like that same browser. These are the rules that most often decide pass vs block.

## One identity for the whole flow

Use the **same User-Agent, TLS fingerprint, IP, and header order** across every request to the target: the challenge fetch, the payload submit, and the follow-up. The `cid` is IP-bound, so solve and spend from the same exit. (The call to this API is out-of-band and does not need to match; everything you send to the *target* does.)

## Replay the returned headers

When a solve returns a `headers` object, send those exact headers to the target. **Never hardcode client hints** or copy them from an unrelated browser capture.

## Client hints

Send high-entropy client hints (`sec-ch-ua-arch`, `-full-version-list`, `-model`, `-platform-version`, `-bitness`) **only after** the origin requested them via an `Accept-CH` response header. Sending them unsolicited contradicts the payload and is a top block cause. Low-entropy hints (`sec-ch-ua`, `-mobile`, `-platform`) are fine by default.

## sec-ch-ua and version

`sec-ch-ua` must match your UA's Chrome major version, and `sec-ch-ua-platform` must match the OS (`"Windows"` / `"macOS"`). Keep the Chrome version within a milestone or two of stable, and when you bump it, change the UA, `sec-ch-ua`, and `sec-ch-ua-platform` together.

## Header order

Real Chrome does not send headers alphabetically (the classic `requests` / `axios` tell). Use a browser header order.

## Accept-Encoding

Chrome sends `accept-encoding: gzip, deflate, br, zstd`. This API also supports gzip: send `Accept-Encoding: gzip` to compress the response.

## Grade on the spend, not the mint

A minted `datadome` cookie is only proven when the next request to the target passes with it. Judge success by the follow-up request, not by getting a cookie.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.vsat.dev/reference/tips.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.