Docs › Dashboard › Chrome Extension (Beta)

Chrome Extension (Beta)

The FourA Chrome extension puts two tools in your browser. The popup sends Chrome through one of your proxy users on the proxy port. The FourA tab in DevTools turns any request a page makes into a ready API call.

The extension is a beta. It isn't in the Chrome Web Store yet, so Chrome installs it in developer mode, and its screens and settings can still change. It needs Chrome version 116 or newer and works on every plan, the Free plan included.

Install

The zip lives in the dashboard: open Extension under Tools in the sidebar and click Download.

  1. Download the zip and unzip it. Keep the folder: Chrome loads the extension from it.
  2. Open chrome://extensions and switch on Developer mode, top right.
  3. Click Load unpacked and choose the unzipped folder.
  4. Pin FourA from the puzzle icon in the toolbar. The icon is grey while FourA is off and shows a green dot while it routes.

Updates

The extension checks for a new version once an hour and when you open the popup, and Check now under Version in the popup's Settings checks right away. When one is out, the popup shows the version with a Download button. Unzip the new version and choose its folder with Load unpacked. FourA replaces itself and keeps your settings, whichever folder the new version comes from. If you unzipped it over the current folder, Reload FourA is enough. Coming from 0.3.1 or older, it installs once as a new card: choose your proxy user again and remove the old card.

Before You Start

  • A proxy user. Create one on the Proxy page of the dashboard: see Proxy.
  • The dashboard signed in, in the same Chrome. The extension reads your proxy users from the dashboard and from nowhere else. When no dashboard tab is open, it opens one in the background to read them and closes it again.

Browse Through FourA

The popup has three pages: Connect, Location and Settings.

Connect

  1. Open FourA from the toolbar and choose the proxy user this browser uses.
  2. Press the big switch.
  3. Read Address sites see. FourA measures that address through the tunnel instead of assuming it from your settings, and shows Your address beside it for comparison.

Traffic this period shows how much of your plan's proxy traffic you've used.

Location

  • Network: Shared (our pool, plan traffic) or Premium (residential, per GB). On Shared, Use premium when shared cannot carry a page takes a premium exit when the shared network can't carry the request. It only fires when your plan includes premium traffic and allowance remains.
  • Country: any country by default. Countries you used recently are one click away.
  • Region, City and Network operator: premium only, after you choose a country.
  • Address: Keep one holds the same exit, New every request changes it on every request, and New address takes a fresh one now. On premium with Keep one, Hold it for sets how long the address is held, in minutes or hours.

The switches behind these choices are the same ones the proxy port documents in Proxy Port.

Settings

  • What goes through the tunnel: Everything except a list, or Only these. example.com covers its subdomains, * works as a wildcard, and 203.0.113.0/24 is a range.
  • Never tunnel the local network or this machine: names with no dot, localhost, .local and the private address ranges stay on your own connection, whatever the list says.
  • Let plain http:// pages use my own connection: the proxy port carries encrypted connections only. Off, a plain http:// page doesn't load. On, it loads over your own connection and the site sees your address.
  • Stop WebRTC from finding a way around the proxy: closes a path a page can use to read your real address while the tunnel is on.
  • Incognito windows: they use the tunnel too. FourA can answer the proxy's password there only when you allow it: chrome://extensions, FourA, Details, Allow in Incognito. Until then Chrome asks you for the password in incognito.
  • Proxy address for other tools: the chosen proxy user as a proxy URL, with its password, to paste into any client that takes one. Treat it like a password.
  • Proxy users: Reload from dashboard picks up proxy users you created or changed. Forget on this computer removes them from this browser.

When the Icon Turns Red

A red icon with a number means the proxy refused that many connections in the last minute. Open FourA to see why. The most common reasons:

  • Too many connections at once: your plan's limit on open tunnels. Parts of the page load again as connections close.
  • Too many new connections this minute: your plan's limit on new tunnels a minute. Give it a minute before reloading, because every retry counts too.
  • This period's proxy traffic is used up or Premium traffic is used up: add traffic on the Billing page or wait for the next period.
  • The proxy is not in your plan: see the plans on the Billing page.
  • The proxy did not accept the password: the proxy user may have been rotated or deleted in the dashboard. Pick it again.
  • Another extension controls the proxy: while another extension holds Chrome's proxy setting, FourA routes nothing. Turn that extension off, then turn the switch off and on.

Your plan's current limits are on the Usage & Limits page.

Turn a Request Into an API Call

  1. Open DevTools on any page and choose the FourA tab, next to Network (behind » when DevTools is narrow). If DevTools was open while you installed FourA, close it and open it again.
  2. Reload the page. The tab lists the page's requests the way Network does. Hide ads and analytics is on by default, and This site only keeps the page's own requests.
  3. Type a text you see on the page into Find in responses to find the request that carries it. Pick the request to see its Headers, Payload and Response.
  4. Under FourA call, choose the engine (Single, Proxy Finder or Browser) and an optional Exit country, then copy the call as curl, Python, Node or MCP. The call carries the headers and cookies the page used.
  5. Click Open in the playground to load the call in the dashboard Playground, or Run through FourA to run it. After a run, The browser got and FourA got show the page's answer and ours side by side.

Right-clicking a request offers the same copies, plus Copy URL, Copy response and Open in a new tab.

The API Key for Runs

Run through FourA uses an API key and its credits. Set it in the tab's Settings:

  1. Click Choose from your dashboard and pick a key, or paste one into Or paste an API key.
  2. Tick Keep the key on this computer to keep it after Chrome closes. Otherwise it stays until Chrome closes.
  3. Forget the key removes it.

The playground opens with the same key chosen when that key belongs to your account. Otherwise it asks you to pick one.

What It Costs

The extension is free. The traffic it sends through our exits counts against your plan's proxy allowance, the same as any other client on the proxy port. Calls you run from DevTools cost what the API charges. See Plans and Metering.

What It Stores and Sends

  • Your chosen proxy user and its password stay on this computer.
  • An API key you choose in the DevTools tab stays until Chrome closes, or on this computer when you ask.
  • Nothing about the pages you visit is stored or sent to us.
  • On its own, the extension asks ipinfo.io (or Cloudflare and then api.ipify.org when that one is busy) which address a site sees, asks foura.ai once an hour and when you open it which version is current, reads your proxy users and the list of countries from your dashboard, and looks up the proxy's address from dns.google or Cloudflare. Everything else happens when you press a button.
  • A call copied with cookies replays the session you're signed into. Treat it like a password and don't paste it anywhere public.

Limits

  • Your browser makes its own encrypted connection through the tunnel, so a site sees our address and your browser. Pages that check who is asking, and full browser rendering, are handled by the API: see Site checks.
  • Chrome is the only browser the extension is built and tested for.
Last updated: September 30, 2026
← Proxy Users