Bot checks
Computers run in data centers. Websites may challenge or restrict traffic from these addresses. A browser proxy can change the exit IP; it does not guarantee that a website will accept automated traffic.Residential IP
A residential IP sends a Linux computer’s Chrome out through a home internet address in the US instead of Orgo’s data center. Some sites that refuse cloud computers accept it, though no site is guaranteed. A home IP doesn’t get past a site’s own bot checks: some sites, such as Reddit, also check the browser and may ask you to sign in.Data each plan includes
Each paid plan includes residential data every month:- Months are UTC. The included amount comes back in full at 00:00 UTC on the 1st. What is left does not roll over.
- Included data is used first, before data you buy.
- A plan includes none while it is paused, and a plan on a trial none until the trial ends.
- If your plan ends, pauses or switches before the 1st, the amount follows the new plan from that day.
- Included data is added to the account a GB at a time, as you use it. While data can’t be added, or once the account reached its limit of 20 GB for the day, what hasn’t been added yet waits. Orgo shows how much is waiting to be added, and it doesn’t count as data left until it is added.
Buy more data
More data is $3 per GB, paid from your Orgo credits or by card, and you can buy as many GB as you need at once: up to 20 GB in one purchase, the most an account can add in a day. In **Settings → Plan & billing**, under **Residential data**, press **Buy data**, pick how many GB, then buy it from your credits or pay the total by card (**Pay $30.00 with card** for 10 GB). From the API, use Buy residential data withgb, which pays from credits.
- Data is sold in whole GB and added at once.
- Data isn’t refunded once added.
- Deleting the account, or a ban for abuse, loses any data left.
- A card payment goes into your credits as a credit purchase, then buys the data from them. If the data can’t be added, the payment stays in your credits. Paying by card needs you signed in to Orgo; an API key can’t.
- An account can add up to 20 GB a day (UTC), every way together: purchases, card payments and the plan’s included data. One purchase adds at most what is left of today, or less while the network has less to add. The ask says how much more fits today.
- At the limit, Orgo says the account reached its limit of 20 GB a day and offers no purchase until 00:00 UTC. The limit is on adding data, not using it.
- An account can make 10 purchases a day (UTC). Card payments you start count too, even ones you don’t finish. After that, buy again from 00:00 UTC.
- A free account can buy too: pay by card, or add credit and pay from it. Starting credit alone can’t buy residential data. Once the account has paid by card or added credit, its whole balance pays, starting credit included.
- The account needs a Linux computer for the data to run on.
- The data belongs to the workspace owner, and only the owner buys it. Every computer in the owner’s workspaces draws on it.
Turn it on
In the dashboard, open the computer’s ⋯ menu, choose Settings, and turn on Residential proxy on the General tab. The row then shows the exit country, the IP and the data used. Its refresh button gets a new IP. When the account has no data left, turning it on asks the owner to buy data first, as many GB as they pick. With the API, while the computer is running:- Turning it on or off restarts Chrome, so open tabs close. Save browser work first.
- Only Google Chrome goes through it. The terminal, other browsers and programs, and calls to the Orgo API keep the data center address.
- The IP is sticky, not fixed. It lasts up to 2 hours, and changes sooner if the home connection behind it goes offline. Ask for a new one any time.
- Exit IPs are in the US only. Any other
countryis400. To ask about other countries, email contact@orgo.ai.
Get a new IP
Send{"enabled": true, "new_ip": true}. Chrome stays open. A computer can get one new IP a minute and 30 a day, and an account 200 a day. Days reset at 00:00 UTC. Past a limit the call answers 429 with residential_new_ip_limited and retry_after, the seconds to wait.
When data runs out
Every computer of the workspace owner draws on one pool of residential data, inquota. Orgo emails the owner when it falls under 0.25 GB and when it runs out. When it runs out, Chrome fails to load pages until there is more. It never falls back to the data center IP on its own. Buy more and pages load again, with nothing to turn back on. To go back to the data center instead, turn it off with {"enabled": false}.
Turning it on with no data left changes nothing and answers the first of these that applies:
409RESIDENTIAL_PURCHASE_IN_PROGRESSwhile a purchase is still finishing. Try again in a minute.503RESIDENTIAL_DATA_UNAVAILABLEwhen nobody can add data to the account right now, whoever asks. Buying, paying or asking the owner won’t help. Nothing is charged. Try again later.429RESIDENTIAL_DAILY_LIMITwithbuy_opens_atwhen the account was added its limit of 20 GB for the day. Nothing more can be added until 00:00 UTC, by anyone. A member reads it too.429rate_limitedwithbuy_opens_atwhen the account’s 10 purchases of the day are used. Nothing can be bought until 00:00 UTC. A member reads it too.402RESIDENTIAL_DATA_NEEDED. To the owner, signed in or with an account-wide key that has full access or Billing write, it carriesprice_centsand anextcall: buy data (the call names 1 GB; send anygbup tomax_gb), or add credit first when credits are short. Anyone else is told to ask the owner.403PLAN_REQUIRED, to the owner of an account with no paid plan and no credit bought. Starting credit alone can’t buy residential data.
Sites that can’t be reached
Some sites are blocked through residential IPs: ticketing, video and music streaming, gambling, torrents and speed tests. The network also blocks some itself, such as banks, payment sites, government sites and mail ports. Chrome showsERR_TUNNEL_CONNECTION_FAILED for them. Orgo never blocks the main webmail and sign-in hosts.
Sites blocked on a residential IP lists every domain Orgo blocks, what is never blocked, and which addresses skip the residential IP.
Check the IP
Get residential proxy returns the last IP seen. Add?check=1 to read it through the proxy now, with changed and checked_at. A check uses a few KB of data, 6 a minute per computer.
A computer with a dedicated IP can’t use a residential IP until the dedicated IP is turned off (409 with residential_dedicated_ip). The residential proxy is for Linux computers only: Windows, Macs and phones answer 400 with residential_proxy_unsupported.
Bring your own proxy
For a running Linux computer,POST /api/computers/{id}/egress/upstream selects a customer-provided HTTP CONNECT proxy:
host is a bare hostname or IPv4 address, with no scheme, port or path. The username cannot contain a colon. tls describes the connection to the proxy and defaults to false when omitted. Each call replaces the whole upstream, so send the password again whenever you change any field. The password is encrypted when stored and omitted from GET /api/computers/{id}/egress/upstream responses.
Selecting a custom upstream enables the computer’s browser relay if it is off. Initial enablement restarts Chrome; save browser work first. When the relay is already on, changing its upstream restarts the relay without restarting Chrome. This setting controls browser traffic, not every program in the computer.
A successful request returns proxy_on and exit_ip, the address Orgo saw through your proxy, or null if it could not read one. A malformed body returns 400. Wake or start the computer first: one asleep in storage returns 409 with the code computer_asleep, and one that is not ready returns 409. Before it keeps a new route, the computer requests https://api.ipify.org through your proxy. If that fails, the request returns 409, the computer keeps its previous route, and Orgo restores the previous selection.
Go back to the data center exit
To stop using your own proxy, send{"mode": "residential"} to POST /api/computers/{id}/egress/upstream. Your proxy and the residential IP are one choice: while your proxy is set, mode reads custom and turning the residential proxy on uses your proxy, so send this first to get a residential IP. That is the field’s default value, and a computer you never set reads "mode": "residential" with "proxy_on": false. The saved upstream is cleared.
If the relay is on, Orgo removes Chrome’s proxy policy, restarts Chrome if it is open, and returns "proxy_on": false. The browser goes out directly from the data center again. On an asleep computer the policy comes off when it wakes. If the relay is off, nothing changes on the computer.