Quick Start Example
Here’s a simple example of how to use Anchor’s built-in proxy:country_code to any supported country (e.g., ‘gb’, ‘de’, ‘jp’).
To experiment with different proxy configurations, visit our Interactive API Reference
Using proxy with tasks
Save proxy settings on the task viatask_default_browser_configuration — a one-time setup. Every run that does not pass a session_id will use this config.
Set it with PATCH /v1/tools/{toolId} or task_browser_default_configuration on POST /v2/tasks/generate:
If you create a session with
POST /v1/sessions and pass its session_id to /run, that session’s config is used — including proxy. The task’s task_default_browser_configuration is ignored for that run.Localization
You can specify a country code for your proxy to route traffic through a specific geographic location. This is useful for accessing region-specific content or testing localized experiences. Thecountry_code parameter accepts country codes in lowercase. See the complete list of supported countries below for all available options.
Region and City-Based Targeting
For even more precise geographic targeting, you can specify bothregion and city parameters. This is only supported for the default proxy type (anchor_proxy).
Important Notes:
- The
cityparameter can only be used whenregionis also provided - If you specify a city without a region, the city parameter will be ignored
- City names: use English, case-insensitive. Both “Los Angeles” and “los-angeles” work.
Supported Countries with their Country Codes
- Anchor Proxy

