> 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/understanding-datadome/dd-cookies.md).

# Cookies & the datadome token

The `datadome` cookie is the proof-of-trust DataDome issues after you pass. Everything orbits it.

* **`cid`**: the client id in the challenge query string and the minted cookie. It is **IP-bound**: DataDome ties it to the exit that requested the challenge. Solve and spend from the *same* exit, or the payload is refused.
* **`datadome` cookie**: set on a successful clear, `Max-Age` up to one year. Send it on subsequent requests to the target and you stay through without re-solving.
* **`ddk` / `hash`**: the tenant's DataDome key and script hash; identify which build you are answering. They appear in the challenge and in the `tags` request.

{% hint style="info" %}
️ A minted cookie is not automatically a *trusted* cookie. The interstitial mints one on every correct solve, but whether it then **spends** (is accepted on the next request) is a separate server-side trust decision driven mostly by exit reputation. Grade on the spend, not the mint.
{% endhint %}


---

# 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/understanding-datadome/dd-cookies.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.