Credential-safe route builder

Build the routing policy once. Put it into the client correctly.

Choose a Databay network, an optional country request, and rotating or sticky behavior. The generator produces a redacted username plus copy-ready configuration for six clients—without asking for your proxy password.

Credentials accepted
None
Generated clients
Six distinct control surfaces
Live verification
Required after generation

Route configuration workbench

Four routing decisions. Six client-ready outputs.

No password entered

  1. 01 · Network

    Residential

    zone-residential

  2. 02 · Location

    United States of America

    countryCode-us

  3. 03 · Persistence

    Rotating pool

    Rotating

  4. 04 · Client

    cURL

    Copy after preflight

1. Choose the network origin

Pick from the approved workload requirement, not as an escalation after a destination refusal.

This requests one network-origin country. It is not a coverage guarantee or a complete localization.

3. Choose route persistence
Valid routing receipt. Availability and the observed exit still require a live preflight.

4. Choose the client surface

Each output preserves that client’s credential boundary.

6 outputs

cURL

shell

: "${DATABAY_PROXY_PASS:?Load DATABAY_PROXY_PASS from your secret store}"
DATABAY_PROXY_USER='USERNAME-zone-residential-countryCode-us'

curl --fail --show-error \
  --proxy 'http://gw.databay.co:8888' \
  --proxy-user "${DATABAY_PROXY_USER}:${DATABAY_PROXY_PASS}" \
  --connect-timeout 10 \
  --max-time 30 \
  'https://databay.com/what-is-my-ip/json'
Credential boundary
cURL receives the username and password separately through --proxy-user.
Ready when
DATABAY_PROXY_PASS is injected by the current process or secret manager.

Gateway

gw.databay.co:8888

Redacted username

USERNAME-zone-residential-countryCode-us

Read the receipt

One gateway, three routing decisions

The gateway stays fixed. Pool, requested country, and optional persistence live in the username. That makes the generated value an auditable routing policy—not proof of a particular exit.

Gatewaygw.databay.co:8888
Username shapeUSERNAME-zone-{pool}-countryCode-{cc}-sessionId-{task}
zone

Selects the product pool.

countryCode

Requests an exit-country estimate.

sessionId

Requests temporary route continuity.

Network decision

Choose from the requirement you can document

A different network is a different test input. It is not a fallback for continuing after a block, challenge, quota, or destination refusal.

NetworkStart here whenLocation controlPersistenceNever infer
Premium residentialAn approved test needs a consumer-network route or detailed location controls.Country plus finer controls where live supply supports them.Rotating, or a requested sticky session up to 120 minutes subject to availability.A household, device, account, person, or guaranteed local experience.
Residential FlexCountry-level sampling is enough and the job fits the lower-cost Flex contract.Country level; actual inventory differs from Premium residential.Rotating, or a sticky session within the current Flex product cap.Premium inventory, city precision, or guaranteed continuity.
DatacenterThe approved workload prioritizes infrastructure throughput and cost.Country availability varies with the datacenter catalogue.Gateway-selected exits; verify any continuity requirement independently.A residential origin, static allocation, or dedicated address.
MobileThe approved test specifically requires a carrier-network route.Country and continent controls subject to current carrier supply.Rotating, or a requested sticky session up to 120 minutes subject to availability.A handset, SIM, subscriber, radio condition, or person.

Session semantics

Sticky is a route request, not stored application state

Reusing a session ID asks the gateway to reuse one live exit for a limited window. The browser or HTTP client still owns cookies, tokens, cache, connection pools, and retries.

Gateway may keep

One exit mapping for the named session, subject to availability and product limits.

Client must keep

Cookies, authorization tokens, request state, connection policy, timeouts, and retry budget.

Rotation may still reuse

A persistent HTTP connection or browser tunnel can carry several requests through one exit.

An exit may still change

An upstream peer can disappear before a requested sticky window ends. Design for an observed change.

Client differences

The routing policy stays stable; authentication does not

Copy the generated shape only after you understand where that client accepts credentials and which proxy behavior its current version documents.

cURL

--proxy plus --proxy-user
Credential boundary
Username and password stay separate from the proxy URL.
Check before production
Command arguments can be visible briefly. Load the password from a protected source.

Python Requests

Per-request proxies mapping
Credential boundary
The generated URL percent-encodes both credential components.
Check before production
The mapping key describes the destination scheme; environment settings can change precedence.

Node.js / Undici

One explicit EnvHttpProxyAgent
Credential boundary
The proxy URL is assembled in process memory from an environment secret.
Check before production
Import fetch and the dispatcher from the same pinned Undici package.

Playwright

Browser or context proxy object
Credential boundary
Dedicated server, username, and password fields answer proxy authentication.
Check before production
The proxy does not isolate cookies, storage, locale, device, or account state.

Selenium

Standard WebDriver proxy capability
Credential boundary
The capability reliably carries host and port, not HTTP-proxy credentials.
Check before production
Use source-IP allowlisting or a separately reviewed authentication mechanism.

Scrapy

request.meta['proxy']
Credential boundary
HttpProxyMiddleware reads a percent-encoded authenticated URL.
Check before production
The standard HTTP handler is the documented path; connection reuse affects rotation.
Production preflight

Add one variable at a time

A generated snippet proves only that the selected controls can be represented. Use this sequence to identify gateway, location, persistence, and destination failures without hiding them through retries.

Verification endpoint

https://databay.com/what-is-my-ip/json

This reports one observed request. It does not certify anonymity, safety, permission, or future availability.

  1. Prove the base gateway first

    Start with the base zone, one Databay-owned diagnostic URL, a bounded timeout, and no country or session flag. A 407 belongs to the gateway-authentication boundary.

  2. Add one routing field

    Request a country and verify the observed exit. The flag changes one network input; it does not set locale, currency, address, cookies, device, consent, or account history.

  3. Add continuity only when required

    Reuse one non-personal session ID for one approved short flow. Persistent connections may reuse an exit even in rotating mode, and an upstream change can end a sticky route early.

  4. Stop at destination controls

    A 401, 403, persistent 429, CAPTCHA, quota, account restriction, or unclear permission is a stop or review signal. Do not change network, country, or session identity to continue.

Technical references

What the client output is based on

References reviewed July 27, 2026. The generated controls follow the official client documentation below. Databay’s gateway and username flags come from the current product and integration contract in this repository.

The generator does not execute the snippet or pin a dependency for you. Verify the output against the exact client, browser, operating system, and product contract used in production.

Continue the task

From a routing receipt to evidence

Choose persistence

Assign client, gateway, and destination state before adding a session.

Open the runbook

Use the maintained guide for setup, environment, TLS, and failure handling.

Probe an endpoint

Separate a point-in-time liveness observation from configuration.

Convert an endpoint

Start from an existing proxy string rather than a Databay routing policy.

Need credentials for the generated route?

Compare the current network contracts first, then load the issued password from a protected runtime secret rather than pasting it into this tool or source code.

Create an accountCompare proxy networks

Use proxies only for authorized work and respect destination terms, quotas, and access controls.