Run from the right network, with managed proxy support
Route authorized runs through managed residential and datacenter proxies so sites render and behave the way your users actually see them.
x-twin-egress: residential/usWhat proxy & geo support does
Some authorized workflows need to originate from a specific network or region — a localized site, a geo-gated dashboard, a high-volume scrape you are entitled to run. Twin integrates managed proxy support (residential and datacenter) so runs egress from the right place, with the routing recorded on every call.
Managed proxy pool
Residential and datacenter egress is integrated, so you don't wire up a separate provider to get the right network.
Pick a region
Pin egress to a region per run so geo-aware sites render the way your users in that region see them.
Recorded on every call
The egress network and region are reported in response headers, so routing is auditable, not a mystery.
For authorized work
Proxy support serves authorized workflows — localized testing, entitled data access, operator-approved automation.
From a goal to deterministic action
- 1Choose egressSet a proxy type and region on the run (or default it per tenant).
- 2Route the sessionTwin opens the browser session through the managed proxy pool.
- 3ExecuteThe run proceeds with the site seeing the chosen network and region.
- 4RecordThe egress network and region are stamped into the response headers.
See it on a real call
Pin egress to a residential US network so a geo-aware site renders the way US users see it.
await twin.agents.run({
goal: "Check the localized price and availability",
url: "https://store.example.com",
proxy: { type: "residential", region: "us" },
});
// → x-twin-egress: residential/us- Choose egressdone
- Route the sessionrunning
- Executequeued
- Recordqueued
What proxy & geo support is
The facts — how it works, what it costs, and the signal you get back on every call.
| Property | Twin Browser |
|---|---|
| Types | Residential, datacenter |
| Region | Per-run or per-tenant |
| Provider | Managed, integrated |
| Signal | x-twin-egress header |
| Scope | Authorized workflows |
| Audit | Egress recorded per call |
Proxy & geo support — common questions
Do I need my own proxy provider?
Can I control the egress region?
Is proxy routing auditable?
The rest of the platform
Credential vault
Per-tenant encrypted secrets are injected into a run when a step needs them — and never enter the model, the logs, or the skill corpus.
Token-efficient DOM state
Twin compiles a live page into a numerically-indexed list of interactive elements under a token budget, so the planner sees signal, not markup.
Live view & session video
Stream the browser session in real time, then keep a durable video of every run for debugging, audit, and proof of what happened.
Make every run cheaper than the last.
Start free, compile your first skill, and watch the marginal cost per run trend toward zero as your agents reuse what they have already learned.