> For the complete documentation index, see [llms.txt](https://docs.databay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.databay.com/introduction.md).

# Introduction

Databay routes your requests through proxy pools you choose from the dashboard or API. Use it when your application needs a different network path, location, or session behavior for normal proxy-compatible traffic.

The current gateway is:

```
gw.databay.co:8888
```

Port 8888 accepts HTTP proxy traffic, HTTPS requests through HTTP CONNECT, and SOCKS5 CONNECT. Most users should start with username and password authentication because the username can carry the network, location, and sticky-session settings for that request.

## Quick test

Replace the placeholders with a proxy user from your Databay dashboard:

```bash
curl -U "YOUR_PROXY_USER-zone-residential:YOUR_PASSWORD" -x gw.databay.co:8888 "https://databay.com/cdn-cgi/trace"
```

If the request succeeds, the response shows the exit IP seen by the destination. Do not publish real proxy usernames or passwords in code, logs, screenshots, or public repositories.

## What you can configure

Databay currently exposes four paid proxy networks:

| Network          | Username zone      | API value | Typical targeting                                      |
| ---------------- | ------------------ | --------: | ------------------------------------------------------ |
| Residential      | `residential`      |         1 | Country, state, city, postal code, ASN, GPS, continent |
| Residential Flex | `residential_FLEX` |         8 | Country                                                |
| Mobile           | `mobile`           |         4 | Country, continent                                     |
| Datacenter       | `datacenter`       |         2 | Country, state, city, postal code, ASN, GPS, continent |

Location filters are best-effort. If a very narrow filter has no live exit available, the proxy server can return an error instead of silently using the wrong target.

## Where to go next

Start with these pages:

* [Network Types](/fundamentals/network-types.md) for the pool names and API values.
* [Authentication](/networks/authentication.md) for username/password and whitelisted IP authentication.
* [Connection String](/networks/proxy-gateways/connection-string.md) for the username parameters.
* [Response codes](/networks/proxy-gateways/response-codes.md) for common proxy server errors.
* [Public API](https://api.databay.com/swagger/index.html) for automation.

Need help with a specific client or target? Contact support at <support@databay.com>.