Identity Primitives

Agent Browser

Give your AI agent a headless Chrome browser with a human-like fingerprint, residential proxy rotation, persistent sessions, and automatic MFA handling. Navigate the web without getting blocked.

Headless Chrome with human fingerprint

Each agent browser session runs a full Chromium instance with a carefully crafted fingerprint that matches real user traffic. Canvas, WebGL, audio, and font fingerprints are all consistent and unique per agent, ensuring your agent passes bot detection systems like Cloudflare, DataDome, and PerimeterX.

The browser supports all modern web standards including JavaScript execution, WebSockets, and service workers. Connect via the Chrome DevTools Protocol (CDP) or use the built-in high-level API.

bash

# Provision an agent with a browser
curl -X POST https://api.humiris.com/v1/agents \
  -H "Authorization: Bearer hum_sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "slug": "web-agent",
    "identity": {
      "browser": true
    }
  }'

# Response
{
  "browser": {
    "cdp_url": "wss://web-agent.browser.humiris.com/cdp",
    "proxy": "residential",
    "fingerprint_id": "fp_x9k2m4",
    "status": "ready"
  }
}

Residential proxy rotation

Every browser session is routed through a residential proxy network. IPs rotate automatically to match natural browsing patterns. You can pin the proxy to a specific geographic region or let Humiris select the best location automatically.

bash

# Configure proxy settings for a browser session
curl -X PATCH https://api.humiris.com/v1/agents/web-agent/browser/config \
  -H "Authorization: Bearer hum_sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "proxy": {
      "type": "residential",
      "country": "US",
      "state": "CA",
      "sticky_session": true,
      "rotate_after": 300
    }
  }'

Cookie and session storage

Browser state is persisted between sessions. Cookies, localStorage, sessionStorage, and IndexedDB data are all saved automatically. When your agent reconnects, it picks up right where it left off, with all login sessions and preferences intact.

bash

# Navigate to a page and capture a screenshot
curl -X POST https://api.humiris.com/v1/agents/web-agent/browser/navigate \
  -H "Authorization: Bearer hum_sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://example.com/dashboard",
    "wait_for": "networkidle",
    "screenshot": true
  }'

# Export cookies for inspection
curl https://api.humiris.com/v1/agents/web-agent/browser/cookies \
  -H "Authorization: Bearer hum_sk_live_..."

MFA/OTP auto-handling

When a website sends an MFA challenge via SMS or email, Humiris can intercept and resolve it automatically. If the agent has a provisioned phone or email, OTP codes are captured and entered into the browser session without any manual intervention.

TOTP-based authenticator codes are also supported. Humiris stores the TOTP seed and generates valid codes on demand.

bash

# Enable MFA auto-handling for a browser session
curl -X PATCH https://api.humiris.com/v1/agents/web-agent/browser/config \
  -H "Authorization: Bearer hum_sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "mfa": {
      "auto_handle": true,
      "sms_agent": "web-agent",
      "email_agent": "web-agent",
      "totp_seeds": {
        "example.com": "JBSWY3DPEHPK3PXP"
      }
    }
  }'

Next steps

Pair Agent Browser with Agent Email and Agent Phone for automatic MFA resolution. Use Agent Computer to run browser automation scripts on a persistent VPS. See the API Reference for all browser endpoints.