> For the complete documentation index, see [llms.txt](https://guide.cryptrend.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.cryptrend.io/chastye-voprosy/spisok/kakie-geo-proksi-vybirat.md).

# Какие гео прокси выбирать?

***

[**Подробнее про настройку прокси - в мануале**](https://guide.cryptrend.io/chastye-voprosy/)

***

Выбор ГЕО прокси имеет некоторое влияние на качество фарма, это обусловленно тем, что трафик каких-либо стран оценивается выше, чем у остальных. Это опциональная настройка, если вы хотите потестировать гео или уже знаете подходящее - то можете ей смело пользоваться.

Но если вы не знаете такого и не хотите тратить время на тесты, то **проще всего использовать Микс, или Европу**. Так проще + проекты не ограничивают использование их сервиса только в той стране, где находится пользователь.

***


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://guide.cryptrend.io/chastye-voprosy/spisok/kakie-geo-proksi-vybirat.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
