The network-and-identity layer for agents

Web presence
for AI agents.

Give every agent a stable, trusted residential identity in the US and UK — so it can log in, act, and finish the task instead of getting blocked.

Get an API key → Read the docs

✓ Ethically sourced IPs ✓ SOC 2 in progress ✓ MCP-native

identity:dedicated

geo:US · residential

session:held 47m

Residva / session-7af3

live

AI agentcomputer-use · browser task

Residva identityheld · geo-pinned · coherent

The open weblogged-in · trusted · stays trusted

✓residential-ISP IP198.51.x.x · US

✓TLS fingerprintJA4 matched

✓HTTP/2 · HTTP/3coherent

✓browser surfacecurrent build

Trusted by teams building the agentic web

Northwind Vantage AI Operant Cartolab Meridian Sundeck

The problem

Agents don't fail at reasoning. They fail at the connection.

An agent can plan a perfect checkout — then never reach the confirmation page, because the web stopped trusting it three steps in.

Datacenter IPs get blocked in minutes

Agents running from cloud servers carry an address every modern site already knows. They're flagged on arrival — before the task even starts.

Rotating proxies break logins

Change the IP mid-task and the session resets. Re-auth fires, carts empty, fraud flags trip. Rotation is the opposite of what a logged-in task needs.

One wrong signal and the session is suspect

Sites score the connection across many layers at once. A TLS fingerprint that doesn't match the browser is all it takes to fail the whole flow.

How it works

One coherent identity, held for the whole task.

Residva assigns each agent a persistent, geo-pinned identity and makes it agree with itself across every layer of the connection — like a real returning visitor.

REQUEST FROM ONE RESIDVA IDENTITY

01 Residential-ISP IP (US/UK)A real consumer address, correctly geolocated. ✓

02 TLS fingerprintMatched to a current, real browser build. ✓

03 HTTP/2 & HTTP/3Protocol behavior consistent with that browser. ✓

04 Browser surfaceHeaders, versions and capabilities all agree. ✓

05 BehaviorSteady, human-plausible pacing across the task. ✓

Every layer agrees, like a real returning visitor.

Dedicated

One identity per agent, reserved — not shared, not rotated. Yours for the task and nobody else's.

Coherent

Consistent across every layer and matched to a current real browser, so nothing in the connection contradicts anything else.

Persistent

The same identity for the entire multi-step task, so logins, carts and verified sessions survive from first click to last.

Capabilities

Infrastructure built for agents that act.

Everything an autonomous session needs to stay trusted — exposed through one clean, agent-native interface.

Dedicated identities

A reserved US/UK residential-ISP IP per agent, held for the task — never pooled, never rotated underneath you.

Cross-layer coherence

TLS, HTTP/2, HTTP/3 and the browser surface kept consistent and current, so every signal tells the same story.

US & UK residential-grade

Accurate, ethically sourced, correctly geolocated presence in the regions your tasks actually run in.

MCP-native + drop-in

Works as an MCP tool and slots into Playwright, CDP and managed browsers without rewriting your stack.

Burn-aware continuity

If an exit degrades mid-task, we migrate without dropping the session identity — the agent never sees a reset.

Observability

Per-session success, health and outcome telemetry — so you can see why a task succeeded, not just guess.

Use cases

Where a held identity changes the outcome.

agentic_commerce

Agentic commerce

Agents that check out and transact without tripping fraud rules — the session stays the same trusted shopper from cart to confirmation.

account_operations

Account operations

Log in and manage a user's own accounts across a full session — settings, subscriptions, support — without re-auth loops.

authorized_workflows

Authorized workflows

Multi-step tasks on SaaS and the open web on a user's behalf, where every step depends on the last one being trusted.

localized_access

Localized access

Consistent US/UK vantage points for verification, testing and QA — see exactly what a real user in-region sees.

Developers

Two lines to a trusted session.

Point your existing tooling at Residva. No rewrite, no new mental model — create a session, hold it for the task, release it when you're done.

✓MCP server included — drop it straight into your agent.
✓Playwright / CDP adapters for managed browsers.
✓session create / hold / release API.
✓Per-session telemetry on every request.

# Route any request through a dedicated US identity
curl -x https://USER:SESSION_TOKEN@gw.us.residva.com:8443 \
     https://example.com

# The same identity is held for the whole session —
# reuse SESSION_TOKEN for every step of the task.
# pip install residva
from residva import Residva
from playwright.sync_api import sync_playwright

rv = Residva(base_url="https://api.residva.com")

# Reserve one coherent identity for the task
session = rv.sessions.create(
    geo="US",
    tier="dedicated",
)

with sync_playwright() as p:
    browser = p.chromium.connect_over_cdp(session.cdp_url)
    page = browser.new_page()
    page.goto("https://example.com/account")
    # ... log in, act, finish — identity held throughout
// residva exposes itself as an MCP tool
{
  "mcpServers": {
    "residva": {
      "command": "npx",
      "args": ["-y", "@residva/mcp"],
      "env": {
        "RESIDVA_API_KEY": "rv_live_•••••",
        "RESIDVA_GEO": "US",
        "RESIDVA_TIER": "dedicated"
      }
    }
  }
}

// Your agent now calls session.create / hold / release

Why Residva

Not a proxy pool. A presence.

The difference between a workaround and infrastructure shows up the moment a task needs to stay logged in.

Capability	Residva Held identity layer	Rotating residential proxies	Raw datacenter / DIY
Built for authenticated multi-step tasks	✓Yes	✗No	✗No
Stable identity across a session	✓Yes	✗No	~Partial
Coherent across all layers	✓Yes	~Partial	✗No
Ethically sourced & compliant	✓Yes	~Varies	–n/a
Agent-native / MCP	✓Yes	~Rare	✗No

Pricing

Priced per identity, not per gigabyte.

You're paying for a trusted presence that finishes tasks — not for bandwidth. Scale identities as your agent fleet grows.

Starter

Self-serve dedicated US/UK identities for early agents and prototypes.

$39/ identity / mo

usage-based · billed monthly

Get an API key

✓Up to 5 dedicated identities
✓US & UK residential-grade
✓MCP server + full API
✓Per-session telemetry
✓Community support

Built to be auditable.

Ethically sourced, consented residential supply; accurate geolocation; and a strict acceptable-use policy limited to authorized actions and public data. Legitimacy is the product — not a footnote.

Ethical IP sourcing SOC 2 (in progress) ISO 27001 (roadmap) GDPR & CCPA aware Acceptable-Use enforced

FAQ

Questions, answered.

A proxy gives you an address. Residva gives you a presence. Three things set it apart: continuity (the same identity for the whole task, never rotated mid-session), coherence (every layer of the connection agrees, matched to a real current browser), and dedication (one identity reserved for your agent). It's built for taking authorized actions, not for scraping pools.

A reserved residential-ISP IP paired with a consistent, coherent fingerprint — held together for the duration of your task. It isn't shared with other customers and isn't swapped out underneath you, so logged-in sessions, carts and verifications stay intact from start to finish.

The United States and the United Kingdom today, with accurate geolocation in both. Additional regions are on the roadmap — enterprise customers can request private regions.

Ethically and with consent, through cleanly registered residential supply. Sourcing is the foundation of the product's legitimacy, so it's documented and auditable — not a black box. Enterprise plans include attestations and detailed sourcing review.

No. Residva is pass-through only and isolated per session. We route the connection; we don't read, log or store the credentials or content that flow over it. Each session is sandboxed from every other.

Three ways: as an MCP tool for agent frameworks, via Playwright / CDP adapters for managed browsers, or as a raw proxy for anything else. Most teams are routing their first trusted session in a few minutes — point your base URL at api.residva.com and go.

Get started

Give your agents a presence that sticks.

Stable, trusted, US & UK residential identities — held for the whole task. Start in minutes.

Get an API key → Talk to us

Web presencefor AI agents.