> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fetchfox.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Automatically pick a proxy

> Ask FetchFox to figure out which proxy to use

Many sites [require proxies](/proxy-basics). Instead of manually choosing a tier for each domain, you can set `proxy` to `auto`.

## The auto proxy parameter

Main endpoint requests (`visit`, `crawl`, `extract`, `scrape`) support:

```json theme={null}
{
  "proxy": "auto"
}
```

Example:

<CodeGroup>
  ```bash curl theme={null}
  curl -X POST https://api.fetchfox.ai/api/crawl \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $FETCHFOX_API_KEY" \
  -d '{
      "pattern":"https://pokemondb.net/pokedex/*",
      "proxy": "auto",
      "maxVisits": 50
  }'
  ```
</CodeGroup>

With `auto`, FetchFox uses domain-level history to balance reliability and cost.

`/api/agent` uses automatic proxying by default.

## What to expect

* First request on a new domain can be slower while data is established.
* Later requests on the same domain are usually faster and more stable.
* If your job still struggles on a domain, switch to an explicit `proxy` tier.

If you need hard control over cost/behavior, use an explicit tier from [Proxy basics](/proxy-basics).