YOUR AGENT. A WAY TO THE WEB.

An agent can call several tools, each with its own network connection. Set the proxy in the browser, HTTP client or script that fetches the page. Changing a chat app’s connection does not prove that its browsing tool uses the same route.

For Claude Code, Codex, Gemini or another host, first identify the tool doing the browsing. A local browser, a shell command and a remotely hosted browser may need different settings. Follow that tool’s documented proxy options.

Start with a small set of public product pages. Ask for the product name, displayed price, currency, source URL and collection time. These are suggested output fields, not an automatic USM export.

• Configure the supplied host, port, protocol and proxy authentication in the tool. Keep credentials in its protected settings, outside prompts and shared transcripts.
• Check the exit IP through that same tool. Open a representative target page and confirm that it contains the expected content, not a sign-in screen or an error.
• Run the sample, review the extracted values against their sources and measure traffic, retries and completion time.
• Expand only after the sample works. Set a request limit and back off when a website asks you to slow down.

Independent page checks can use changing exits. A sequence that depends on the same session needs continuity instead: changing IP between steps can interrupt a workflow.

A sticky session requests the same exit for a period; it is not a permanent IP or a guarantee against disconnection. Confirm the session options available for the USM product before relying on a particular duration.

USM catalogue prices use IP count or a GB allowance. Model calls, hosted browsers and extraction services have their own fees. One prompt may open many pages and load images or repeat requests, so prompt count is not a reliable traffic estimate.

Measure a representative run, then use its traffic per completed task to estimate a larger batch. Include the resources your task actually needs and leave room for retries; do not assume a fixed number of pages per GB.

This guide describes standard proxy configuration. USM does not currently offer a public scraping API, an installable Claude / Codex Skill or a public MCP service. Those release pages will identify supported operations and setup instructions when available.

USM supplies the proxy connection; it does not supply your model, render pages or return automatically parsed data. A proxy also does not grant access to a model subscription or to private website content.