Skip to main content
Anchor provides proxy configurations to access websites from different geographic locations, configurable down to the city level. Use Bring Your Own Proxy or Anchor’s built-in proxy for localization.
Anchor Browser infrastructure is fully hosted in the US. For GDPR compliance, upgrade to the Growth tier or contact support.

Quick Start Example

Here’s a simple example of how to use Anchor’s built-in proxy:
This creates a browser session using Anchor’s built-in proxy. You can change 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 via task_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.
See Run a Task for the full run flow.

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. The country_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 both region and city parameters. This is only supported for the default proxy type (anchor_proxy). Important Notes:
  • The city parameter can only be used when region is 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