Task-scoped sessions
Bind cookies, proxy session identifiers, and browser storage to one job so context does not leak between agents.
Agent network control
AI agent proxies with explicit routes, session limits, and observable outcomes
Separate planning from network execution. Assign each authorized task a route policy, isolate state, validate the response, and return evidence the agent can reason about.
01Collectpublic source
02Validatestatus + locale
03Transformstructured record
04DeliverAPI or pipeline
A network contract for every agent task
The agent chooses an allowed task; the execution layer enforces routing and returns structured evidence.
🧭
Plan
Resolve the permitted target, required geography, session mode, timeout, and success criteria.
🔐
Isolate
Create a task-scoped browser or HTTP context without reusing cookies or credentials across unrelated jobs.
🌐
Route
Apply rotating or time-bounded sticky proxy credentials according to the task contract.
✅
Validate
Classify status, content markers, locale, challenge pages, and target-side denial before accepting data.
🧾
Return evidence
Return structured fields, route metadata, retry reason, and a redacted artifact to the orchestrator.
Authorization, destination policy, concurrency, and retry limits remain authoritative outside the model.
Controls that keep agent browsing reviewable
Deterministic route policy
Choose geography and rotation before execution instead of allowing the model to improvise credentials.
Bounded retry budgets
Retry temporary network failures only; stop on authentication failures, explicit denial, or repeated challenges.
Structured response contracts
Return status, observed locale, extraction result, and evidence fields that downstream agents can validate.
Credential redaction
Keep proxy passwords and application secrets out of prompts, traces, screenshots, and support logs.
Frequently asked questions
Does the AI model receive the proxy password?+
It should not. Store credentials in the execution service and let the model select an approved route profile or task policy rather than raw secrets.
When should an agent use a sticky session?+
Use a short sticky session for a stateful multi-step flow. Use rotation for independent fetches where no cookie or page continuity is required.
How should an agent react to a 403 or challenge page?+
Classify the response, preserve a small redacted artifact, and stop or escalate according to policy. Blindly rotating and retrying can increase cost and risk.
Can this be used for private or authenticated data?+
Only where the user has authorization and the workflow has explicit access, retention, and privacy controls. The default design should target public data.